abdera-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James M Snell (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (ABDERA-210) Abdera Servlet Always uses ServletOutputStream rather than the Writer interface.
Date Mon, 04 May 2009 21:32:30 GMT

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

James M Snell resolved ABDERA-210.
----------------------------------

    Resolution: Fixed

Fix checked in

> Abdera Servlet Always uses ServletOutputStream rather than the Writer interface.
> --------------------------------------------------------------------------------
>
>                 Key: ABDERA-210
>                 URL: https://issues.apache.org/jira/browse/ABDERA-210
>             Project: Abdera
>          Issue Type: Bug
>    Affects Versions: 0.4.0
>         Environment: NA
>            Reporter: Michael Ahern
>            Assignee: James M Snell
>
> The AbderaServlet always uses the 'Abdera Servlet Always uses ServletOutputStream rather
than Writer interface.  This leads to unnecessary buffering of data.
> Further down the stack call this leads to issues with 'SimpleResponseContext' and its
derivatives, where by the 'OutputStream' is wrapped by a 'OutputStreamWriter' class.   For
example, since the 'OutputStreamWriter' is buffering data, users of the 'SimpleResponseContext'
are always required to 'flush()' the output stream.  
> Users of the 'SimpleResponseContext' can get burned by because the OutputSteamWriter
not getting flushed.
> One intermediate solution is to have the 'SimpleResponseContext' automatically flush
the 'OutputStreamWriter'.

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


Mime
View raw message