First off let me preface this in saying I'm not a Java guy, least not just yet. To my understanding there are a couple options you have that may or may not work for your given situation.
1. Polling - not really much fun and pretty inefficient. 2. Setting up a version system for the data that needs to be updated. For instance a contact list that every time it is updated increments the last version. You send you updated contact to GDS it see's the version you're updating isn't the current version and alerts you etc. 3. Setup your own Java messaging via whatever app server you're using. So you update X contact it alerts the message service that anyone with X contact should update to the new one you updated. More or less I believe thats all FDS does. Mind you they have it all setup nice and clean for you already. I know Red5 has a JMS system built into it that Flex can consume, so assuming Flex can connect to any JMS it would just be a matter of setting it up and making the appropriate announcements across the JMS within your update service etc. It really comes down to how "real time" you need your data to be. The first to options would be pretty easy to implement. The 3rd, as I'm not a Java guy once again, I'm not 100% sure about. You might try contacting someone over at GDS as I'm sure if nothing else it would make for an awesome feature request if they're not already working on something like that. Out of curiosity how are you liking GDS? Currently the project I am working on uses AMFPHP and I was thinking of moving to FDS(big $ maybe there) or something open source like GDS for the next version of the project. I haven't seen too many people using GDS yet so any info on your experiences thus far would be greatly appreciated. - Kyle
