Hi Mark, http(s) transport uses XStream (http://xstream.codehaus.org/) to marshall/unmarshall messages and it should do just fine with binary data. As for performances, they are the same as in all similar systems (xml over http). We don't have any metrics though, so if you come up with some please share them. Also, please report any issues you encounter, since we're looking to improving this transport in future releases.
Cheers -- Dejan Bosanac Open Source Integration - http://fusesource.com/ ActiveMQ in Action - http://www.manning.com/snyder/ Blog - http://www.nighttale.net On Fri, May 29, 2009 at 9:46 PM, MarkThomsen <thoms...@earthlink.net> wrote: > > Dejan, > > The reference says "The HTTP and HTTPS transports are used to tunnel over > HTTP or HTTPS using XML payloads." Does this mean binary data is > marshalled/wrapped into XML (blob, uuencode, etc.)? Or does it mean that > XML text messages are sent, and binary messages (like serialized POJOs) are > not --- a restriction on messages when using HTTP(S) transport? > > The reference (and documentation, threads) are ambiguous. > > If binary is fine then what is experience with performance, message size, > and such? Lessons for efficient use and limits. > > Mark > > > Dejan Bosanac wrote: > > > > Hi Mark, > > > > you can try using http transport > > > > http://activemq.apache.org/http-and-https-transports-reference.html > > > > if you expirience any problems with this transport, you can try latest > 5.3 > > snapshots as there were couple of improvements in this area recently. > > > > Cheers > > -- > > Dejan Bosanac > > > > -- > View this message in context: > http://www.nabble.com/JMS-over-HTTP-tp23750470p23785990.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > >
