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? On Sun, May 16, 2010 at 2:20 PM, sasuke <[email protected]> wrote: > > > > > Evan Klein wrote: > > > > You are looking for messaging services. Messaging services come out of > the > > box with BlazeDS and Livecycle Data services. > > > > Both products have a Java API for creating the producer components to > push > > messages down to clients. > > > > Livecycle , however is about $40K / CPU and has advanced functionality > > such > > as RMTP channels, guaranteed message delivery, throttling, etc. > > > > Give this an example a try > > > http://learn.adobe.com/wiki/display/Flex/Creating+a+BlazeDS+messaging+application+in+Flex+Builder > > > Hmm..I did hear about BlazeDS before starting with this project but I was > under the impression that the interaction between the Flex client and the > server happens using HTTP given that BlazeDS is deployed as a web > application, no? Or is it that after being deployed, BlazeDS sets up a > server socket which listens to AMF messages on a specific port? Is this in > the end AMF3 data polling over HTTP? > > TIA, > sasuke > > -- > View this message in context: > http://old.nabble.com/Application-requiring-streaming-data-tp28550128p28576398.html > > Sent from the FlexCoders mailing list archive at Nabble.com. > > >
