activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "james strachan (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (AMQ-637) Enhance ActiveMQInput/Outputstream to use a real TCP connection.
Date Wed, 07 Mar 2007 16:12:21 GMT

     [ https://issues.apache.org/activemq/browse/AMQ-637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

james strachan resolved AMQ-637.
--------------------------------

    Resolution: Fixed

Its probably better just to migrate the code to use the new BlobMessage API in 4.2 as this
allows for efficient out of band communication; either direct producer <-> consumer
or from producer -> broker and broker -> consumer

> Enhance ActiveMQInput/Outputstream to use a real TCP connection.
> ----------------------------------------------------------------
>
>                 Key: AMQ-637
>                 URL: https://issues.apache.org/activemq/browse/AMQ-637
>             Project: ActiveMQ
>          Issue Type: Improvement
>            Reporter: Robert Newson
>             Fix For: 4.2.0
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message