|
Hi guys, finally i'm trying Red5 on my reduced spare time. :) Today i've followed some video tutorials (flashextensions), and it's becoming more clear to me how everything works with Red5. My main objective with Red5 is to keep my RIAs synchronized with the data on the server. If one client adds something to the database, the others receive the change without having to pool data from time to time. For learning more about Red5, i want to change CastingOffice, by replacing the server-side code (PHP with AMFPHP) for Red5, and giving the server the capability of pushing new data to the clients. My client side code is based on ARP (Commands use ServiceDelegates (mx.remoting.service) returned by the ServiceLocator to retrieve Value Objects from the server, adding them to the ModelLocator that fires an event saying that that specific model has changed, allowing registered views to update their screen), and i want to change it as less as possible. My biggest problem right now is to find how to give the server initiative to alert all the clients, and how to adapt the client-side code to work with Red5 and the synchronization features, changing it as less as possible. Any advices to help me starting with this? Thank you all! João Saleiro --
|
_______________________________________________ Red5 mailing list [email protected] http://osflash.org/mailman/listinfo/red5_osflash.org
