[ 
http://issues.apache.org/jira/browse/DIRMINA-229?page=comments#action_12424945 
] 
            
Niklas Therning commented on DIRMINA-229:
-----------------------------------------

I think this problem is very bad since things could get very, very messed up if 
you wrap one of these stream instances in e.g. a BufferedOutputStream. I'm not 
sure whether we want non blocking writes here. If we use join() as suggested in 
Oleg's patch we could also check isWritten() on the WriteFuture and throw an 
IOException if it couldn't be written. WDYT?

BTW, the patch looks great. I have no objections. But I would like to add the 
isWritten() check as well. I'll go ahead and apply it right away.

> IoSessionOutputStream write methods should not return before the I/O 
> operation is fully completed
> -------------------------------------------------------------------------------------------------
>
>                 Key: DIRMINA-229
>                 URL: http://issues.apache.org/jira/browse/DIRMINA-229
>             Project: Directory MINA
>          Issue Type: Bug
>    Affects Versions: 0.9.4
>            Reporter: Oleg Kalnichevski
>         Attachments: mina-bio-stream.patch
>
>
> IoSessionOutputStream write methods return before the I/O operation is fully 
> completed, which causes issues in protocol handlers based on blocking 
> InputStream/OutputStream model. Is it a desired behaviour?
> Per discussion with Peter Royal on the HttpComponents mailing list I am 
> working on a simple HTTP server based on MINA and HttpComponents Core.  
> HttpCore does not work with the latest SVN snapshot of MINA without this 
> patch (attached)
> Oleg

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to