[
https://jira.jboss.org/jira/browse/JBREM-1009?page=com.atlassian.jira.plu...
]
David Lloyd closed JBREM-1009.
------------------------------
Resolution: Done
I set up stream serializers to always use AllocatedMessageChannels. The reasoning is that
streams may be emulated over a message channel much more easily than the other way around;
also in the stream serializer implementations I've developed thus far, a stream
channel has never been called for.
Streaming should work with packet-based channels as well as
stream-based channels
---------------------------------------------------------------------------------
Key: JBREM-1009
URL:
https://jira.jboss.org/jira/browse/JBREM-1009
Project: JBoss Remoting
Issue Type: Task
Security Level: Public(Everyone can see)
Components: r3 api
Reporter: David Lloyd
Assignee: David Lloyd
Fix For: 3.0.0.Beta1
OutputStreams and Writers are trivially implemented using streams - writes to the remote
object are simply propagated across to channel. Other types of streams are more difficult
to implement this way. InputStream for example has two types of messages - a data chunk
and an exception chunk. Because of this, some basic framing is necessary; with only
support for streams, this framing must take place within the stream handler which is a
pain to implement.
So, a stream serializer should be able to register itself as a byte stream handler (using
a StreamChannel) or a message stream handler (using a MessageChannel).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira