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 On Thu, May 13, 2010 at 1:10 PM, sasuke <[email protected]> wrote: > > > > Hi all, > > I'm currently working on an use case/application which is something along > the following lines: > When the user successfully logs in the application, he would be shown a > graph/some statistical data. This data would be real time in the sense that > it would be updated with a granularity of around 100ms at the server which > needs to be pushed ASAP to the client. > > Now, using services like WebServices, HttpService etc. would be a > performance killer in my case given the time/resources taken during > connection creation/tear down. Using long lived connections for HTTP might > end up failing if the proxy server decides to "cache" the response till the > stream is closed. Also, given that HTTP is a request oriented protocol, the > client would have to "beg" for changes before the server sends them to the > client. > > So my question is: Which would be the most performant and viable solution > when it comes to retrieving streaming data or the server continuously > pushing data to the client once the client registers itself? It would be > much appreciated if you could share your similar experiences with such > requirements. > > TIA, > sasuke > -- > View this message in context: > http://old.nabble.com/Application-requiring-streaming-data-tp28550128p28550128.html > Sent from the FlexCoders mailing list archive at Nabble.com. > > >
