[jboss-jira] [JBoss JIRA] Updated: (JBREM-597) Allow access to underlying stream in marshaller with socket transport

Tom Elrod (JIRA) jira-events at jboss.com
Mon Sep 11 11:01:44 EDT 2006


     [ http://jira.jboss.com/jira/browse/JBREM-597?page=all ]

Tom  Elrod updated JBREM-597:
-----------------------------

          Component/s: transport
    Affects Version/s: 2.0.0.GA (Boon)
             Priority: Critical  (was: Major)

> Allow access to underlying stream in marshaller with socket transport
> ---------------------------------------------------------------------
>
>                 Key: JBREM-597
>                 URL: http://jira.jboss.com/jira/browse/JBREM-597
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: transport
>    Affects Versions: 2.0.0.GA (Boon)
>            Reporter: Tim Fox
>         Assigned To: Tom  Elrod
>            Priority: Critical
>             Fix For: 2.2.0.Beta1 (Bluto)
>
>
> Currently the ClientSocketWrapper::createOuputStream always returns an ObjectOutputStream wrapping the underlying socket ouput stream.
> This ends up getting passed into the marshaller.
> With messaging we'd like to use the underlying socket output stream directly in the marshaller - i.e. we don't want to have to write through an object output stream.
> This is because the object output stream adds some overhead in terms of the amount of stuff written to the underlying stream..
> A similar reasoning applies to InputStream too.
> Any chance of changing the socket transport to pass in the underlying socket stream, not an object output/input stream?

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

        



More information about the jboss-jira mailing list