Hi Kyle, for now I have implemented a polling-mechanism. But as you already said, that's a pretty inelegant solution. And it brings pain:
Now I have to find a way to prevent my DataGrid to jump back to the top every time the data reloads. If the data is reloaded e.g. every 5 secs one can barely scroll without beeing interrupted... Same goes for the sort-order. Until now I only found a solution for the scrolling (write a own render()-operation for the DataGrid in which you set the scroll-position back to the saved scroll-position). I also wrote to Franck Wolff from GDS about Data Push. He said that he planned it but that he hasn't a particular roadmap. Your idea with the version system would at least save some reloads. Hmm, I like to use the FDS's Messaging Services very much, but the licensing is really to expensive. GDS is a very interesting Open Source project. So far I only used them with Pojos. Version 0.2 works for me and it is the best free/open alternative to FDS for the project I'm working on. Soenke --- In [email protected], "kyle.vanvranken" <[EMAIL PROTECTED]> wrote: > > 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 >
