[jira] Resolved: (SLING-1897) SlingHttpServletResponseImpl.flushBuffer() does not flush parent response

["Felix Meschberger (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SLING-1897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Felix Meschberger resolved SLING-1897.
--------------------------------------

    Resolution: Fixed

Rev. 1062702: Better coordinate internal output buffer handling with servlet container buffering:
  - internal commit check for resetBuffer and reset
  - setting the buffer size for the engine also sets the same buffer size for the servlet container
  - flushBuffer() also calls flushBuffer() on the servlet container's response
     (after flushing the internal buffer, if any)
  - reset() also resets any internal (engine) buffered data in addition
     to resetting the servlet container's response
  - resetBuffer() also resets servlet container's buffer in addition to
     the internal buffer


> SlingHttpServletResponseImpl.flushBuffer() does not flush parent response
> -------------------------------------------------------------------------
>
>                 Key: SLING-1897
>                 URL: https://issues.apache.org/jira/browse/SLING-1897
>             Project: Sling
>          Issue Type: Bug
>          Components: Engine
>    Affects Versions: Engine 2.1.0
>            Reporter: Tobias Bocanegra
>            Assignee: Felix Meschberger
>             Fix For: Engine 2.2.0
>
>
> example:
> slingResponse.setBufferSize(0);
> slingResponse.getOutputStream().write(123);
> slingResponse.flushBuffer()
> does actually bypass the buffer in ContentData, but the flushBuffer is not passed to the wrapped response (neither is setBufferSize())

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.