You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Hiram Chirino (JIRA)" <ji...@apache.org> on 2006/06/15 05:14:02 UTC
[jira] Updated: (AMQ-637) Enhance ActiveMQInput/Outputstream to use
a real TCP connection.
[ https://issues.apache.org/activemq/browse/AMQ-637?page=all ]
Hiram Chirino updated AMQ-637:
------------------------------
Fix Version: 4.2
This could take a bit of thought to implement correctly. Putting out till 4.2.
> Enhance ActiveMQInput/Outputstream to use a real TCP connection.
> ----------------------------------------------------------------
>
> Key: AMQ-637
> URL: https://issues.apache.org/activemq/browse/AMQ-637
> Project: ActiveMQ
> Type: Improvement
> Reporter: Robert Newson
> Fix For: 4.2
>
>
> 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:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira