You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "james strachan (JIRA)" <ji...@activemq.org> on 2006/03/16 19:56:25 UTC
[jira] Commented: (AMQ-637) Enhance ActiveMQInput/Outputstream to
use a real TCP connection.
[ http://jira.activemq.org/jira//browse/AMQ-637?page=comments#action_35766 ]
james strachan commented on AMQ-637:
------------------------------------
Sounds fine with me :)
BTW is the idea that the socket will only be open for the duration of the input stream, so that the transfer is independent of the underlying JMS connection?
We do need to chunk the message on the broker side to avoid it having to load the whole stream into RAM; is this OK with you?
> Enhance ActiveMQInput/Outputstream to use a real TCP connection.
> ----------------------------------------------------------------
>
> Key: AMQ-637
> URL: http://jira.activemq.org/jira//browse/AMQ-637
> Project: ActiveMQ
> Type: Improvement
> Reporter: Robert Newson
>
>
> Currently the ActiveMQInputStream and ActiveMQOutputStreams chunk large messages into 64k chunks.
> Instead of that, could the act of calling getInputStream(Destination) negotiates a new TCP socket connection? Using ActiveMQ will still give us location transparency, but will the full streaming power of TCP.
> I spoke with Hiram about this and he thought it would be a fairly simple enhancement. I'm happy to work with him on this as we have a strong need for this functionality.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.activemq.org/jira//secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira