Real Time Client Update - Suggestions

I have a client that needs to have their Flex client respond with real-time data as a particular table is being updated in the mysql database.  The project is running through MAMP (WAMP eventually) with PHP. What ideas are out there?  I've looked at Weborb - and it has no real time updating for PHP.  Also I checked out LiveCycle - heard that is astronomical in cost to license. Help.... Thanks!

Have you looked into BlazeDS? On Wed, 2010-05-05 at 12:52 -0400, Kim Hoopingarner wrote: > I have a client that needs to have their Flex client respond with real-time data as a particular table is being updated in the mysql database.  The project is running through MAMP (WAMP eventually) with PHP. > > What ideas are out there?  I've looked at Weborb - and it has no real time updating for PHP.  Also I checked out LiveCycle - heard that is astronomical in cost to license. > > Help.... Thanks!

OK- Glad you mentioned BlazeDS.  Here's my confusion - I'm not sure what to download to get started.  I already have MAMP running for this project.  The turnkey sounds like it has another apache server - which I don't think is what I want?   Thoughts?

> OK- Glad you mentioned BlazeDS.  Here's my confusion - I'm not sure what to download to get started.  I already have MAMP > running for this project.  The turnkey sounds like it has another apache server - which I don't think is what I want?   Thoughts? BlazeDS can be installed like any other WAR/EAR into an existing J2EE app server. But you will need a J2EE app server to run it. It comes bundled with Tomcat. Also, BlazeDS doesn't provide real-time push like LCDS does. LCDS provides the ability to use RTMP to push messages to the server. BlazeDS supports HTTP polling by the client - at a default of every 8 seconds if I recall correctly. That's good enough for many uses, though. LCDS is very expensive. To learn more about how you'd use BlazeDS for this, read the "Message Service" section off the documentation. To learn more about how your Flex client code would work, read about the Producer and Consumer classes. http://learn.adobe.com/wiki/display/Flex/Creating+a+BlazeDS+messaging+application+in+Flex+Builder Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ http://training.figleaf.com/ Fig Leaf Software is a Veteran-Owned Small Business (VOSB) on GSA Schedule, and provides the highest caliber vendor-authorized instruction at our training centers, online, or ons

Sorry but BlazeDS does provide real-time data push like LCDS, but not scalable like his big brother. If you use StreamingAMF channels (or long polling) you'll have real-time data push. You can also configure a polling channel that provides piggy back and you'll have an almost real-time. João Fernandes On 5 May 2010 19:20, Dave Watts <dwatts@figleaf.com> wrote: ----- Excess quoted text cut - see Original Post for more -----

Thanks for the tips.   So here's my ignorance showing of what Flex 3 can do for me "as is"... But if I can deal with a small delay - do these "channels" supply the answer?   If so - are there any examples you might share so that I can understand how to configure.  I'm really green to this, if you can't tell. Kim

> Sorry but BlazeDS does provide real-time data push like LCDS, but not > scalable like his big brother. If you use StreamingAMF channels (or > long polling) you'll have real-time data push. You can also configure > a polling channel that provides piggy back and you'll have an almost > real-time. No need to be sorry! I'm not very familiar with StreamingAMF. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ http://training.figleaf.com/ Fig Leaf Software is a Veteran-Owned Small Business (VOSB) on GSA Schedule, and provides the highest caliber vendor-authorized instruction at our training centers, online, or onsite.

On 05-05-2010 20:04, Dave Watts wrote: > No need to be sorry! I'm not very familiar with StreamingAMF. >     StreamingAMF was a new channel added the same time they provided piggyback capabilities to the amf-polling channel, can't remember exactly when it was added. Kim, the channels itself aren't much important, they just differ from the kind of «real-time» you really need for you app, they are just a endpoint to deliver messages to the client. The only thing you'll need it will be consumers and producers (if clients can broadcast messages) and server side, a way to call the sendMessage using the java API. Of course it would be a lot easier for you to use CF since it already has a specific method to broadcast messages to all connected clients. Now the question is, how many concurrent users are you expecting? João Fernandes