[jboss-jira] [JBoss JIRA] Closed: (JBREM-692) Let marshallers/unmarshallers construct their preferred streams.

[Ron Sigal (JIRA)]

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

Ron Sigal closed JBREM-692.
---------------------------

    Resolution: Done

Unit tests:

    org.jboss.test.remoting.marshall.SocketPreferredStreamMarshallerTestCase 
    org.jboss.test.remoting.marshall.BiocketPreferredStreamMarshallerTestCase 

The tests and code changes have been committed to remoting_2_x and HEAD.

The tests have passed on cruisecontrol.

> Let marshallers/unmarshallers construct their preferred streams.
> ----------------------------------------------------------------
>
>                 Key: JBREM-692
>                 URL: http://jira.jboss.com/jira/browse/JBREM-692
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions:  2.2.0.Beta1 (Bluto)
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For:  2.2.0.Beta1 (Bluto)
>
>
> In response to JBREM-597 the socket transport was changed to provide raw socket streams to the marshaller layer.  This leads to several issues:
> 1. JBREM-623
> 2. JBREM-631
> 3. The result of JBREM-597 is that (un)marshallers like Serializable(Un)Marshaller that use object streams need to recreate object streams with each invocation, which is time consuming.
> A solution, suggested by Tom Elrod, is to allow the marshaller layer to construct the streams it prefers to work with, which can then be cached at the transport layer.

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