You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Tobias Bocanegra (JIRA)" <ji...@apache.org> on 2010/12/13 13:00:10 UTC

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

    [ https://issues.apache.org/jira/browse/SLING-1897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12970787#action_12970787 ] 

Tobias Bocanegra commented on SLING-1897:
-----------------------------------------

simple patch that works for me:

Index: src/main/java/org/apache/sling/engine/impl/SlingHttpServletResponseImpl.java
===================================================================
--- src/main/java/org/apache/sling/engine/impl/SlingHttpServletResponseImpl.java	(revision 1045074)
+++ src/main/java/org/apache/sling/engine/impl/SlingHttpServletResponseImpl.java	(working copy)
@@ -129,6 +129,7 @@
     @Override
     public void flushBuffer() throws IOException {
         getRequestData().getContentData().flushBuffer();
+        getResponse().flushBuffer();
     }
 
     @Override


> 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
>
> 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.