BlazeDS and LCDS use AMF for messaging/remoting - which is more compressed than plain text such as XML. Mete did correct some of my information. LCDS uses RTMP which is socket based. However, this assumes you have $40K or so to invest in LCDS. If you don't or do, I would suggest you look at a company called Farata Systems and their product called Clear Toolkit. They have taken BlazeDS and are extending it to implement reliable/guaranteed messaging.
Take a look at this blog post by them: http://flexblog.faratasystems.com/2010/03/15/open-source-alternatives-to-livecycle-data-servcies <http://flexblog.faratasystems.com/2010/03/15/open-source-alternatives-to-livecycle-data-servcies> On Mon, May 17, 2010 at 1:18 PM, sasuke <[email protected]> wrote: > > > > Hi Evan, > > Correct me if I'm wrong but: > - HTTP is a plain text protocol and hence suffers from verbosity which is > almost never acceptable when developing real time solutions (not to mention > the header information transmitted) > - HTTP is a request-response protocol so any kind of "streaming" solution > provided by a HTTP based protocol would be a diluted simulation at best. > > Hence my search for a protocol which actually was meant for streaming. > > Regards, > sasuke > > > Evan Klein wrote: > > > > All of these solutions happen over HTTP. I'm not aware of a messaging > > solution that does not use HTTP. > > > > Why the requirement to not use http? > > > > -- > View this message in context: > http://old.nabble.com/Application-requiring-streaming-data-tp28550128p28586237.html > > Sent from the FlexCoders mailing list archive at Nabble.com. > > >
