The problem I'm having is this: I've done a lot of flash projects, but none where I've needed to control many hundreds of clients via server polling/messaging. I don't have a sense of what protocol to use in order to get lightweight (hopefully reliable) communication from server to clients that can be done without spending much on server licenses.
Would moving to something like AMFast? or XML Sockets provide significant benefit? Thank you! Steven ________________________________ From: Peter Ginneberge <[email protected]> To: Flash Coders List <[email protected]> Sent: Friday, March 9, 2012 10:54 AM Subject: Re: [Flashcoders] Should I use BlazeDS for this? WebOrb seems to have RTMP in all their editions (including the free one). http://www.themidnightcoders.com/products/weborb-for-java/product-editions.html regards, Muzak ----- Original Message ----- From: "Dave Watts" <[email protected]> To: "Steven Loe" <[email protected]>; "Flash Coders List" <[email protected]> Sent: Friday, March 09, 2012 6:08 PM Subject: Re: [Flashcoders] Should I use BlazeDS for this? >> When we have network slowdowns, polling sometimes fails and the >> project hangs. Is Blaze/LiveCycle well behaved on thin networks? Is it >> more robust than polling under these conditions? > > To add to Henrik's answer, LiveCycle supports async (push) via RTMP, > but BlazeDS doesn't include RTMP support. It does support HTTP > "long-polling", which is about as efficient as you get without actual > async communication: > > https://en.wikipedia.org/wiki/Push_technology#Long_polling > > Dave Watts, CTO, Fig Leaf Software _______________________________________________ Flashcoders mailing list [email protected] http://chattyfig.figleaf.com/mailman/listinfo/flashcoders _______________________________________________ Flashcoders mailing list [email protected] http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
