A bit of history: GDS was created because FDS was too expensive and, much more important, because it didn't integrate well with well known persistence API (EJB3/Hibernate) and didn't provide any lazy-loading mecanism. That's why, from the very beginning, I have created this "transparent externalization" feature (especially the HibernateExternalizer one) that serializes and keeps private all persistent related bean's fields (id, version, etc). Then, gas3 (ths GDS code generator) was designed in order to avoid the tedious task of writing manually Externalizable AS3 beans.
How BlazeDS compares to GDS: surprisingly, from a strict remoting point of vue, BlazeDS is exactly what GDS has always wanted to be: classical AMF3 remoting with RemoteObjects and a new Comet based channel with AMF3 objects exchanged between Producers and Consumers over HTTP (no RTMP). On the other hand, from a persistence point of vue, BlazeDS does not include any data management features, so GDS brings a very important missing feature: EJB3 persistence with lazy-loading support.
A bit of strategy: the first release of BlazeDS (LGPL3, with sources) is announced for early 2008 (no precise schedule...) The best strategy for us is to release GDS 1.0 as soon as possible (before the end of January) and to wait for BlazeDS public sources. Then, we'll be able to either copy-paste some BlazeDS nice code into GDS (same license!) or to contribute with externalizers+lazy-loading+gas3 to BlazeDS features (if Adobe is ok) or even to release GDS has a kind of BlazeDS plugin (no idea about how this will be possible).
Hi all (here is my new thinking): 1. A bit of history: GDS was created because FDS was too expensive and, much more important, because it didn't integrate well...
I agree. I think Adobe will open source a lot of things, but will keep a few things in the commercial version. These few things won't be a problem for some...
Just a try to have an idea of Adobe position : http://www.adobe.com/cfusion/webforums/forum/messageview.cfm?forumid=72&catid=667&threadid=1322733&enterthread=y...
Hi Frank, Did you have time to give a look to BlazeDS source code (http://opensource.adobe.com/wiki/display/blazeds/BlazeDS). What do you plan for GraniteDS...
Hi, I had a quick look at BlazeDS sources. It's a really good thing to have now access to RemoteObject.as source code (among many others). I don't have any...
Thank you Franck. This is all I needed to know. From my perspective, Flex and Seam are THE two most compelling frameworks available today (admittedly, I...
BlazeDS will kill GraniteDS - actually it was my first thought when I saw the post on TechCrunch about Adobe releasing BlazeDS (it was quickly removed after...
Well, just to add my own comment to this! I also think BlazeDS won't give us everything we are now used to (I'm referring to Hibernate Externalizer and Gas3...
Hi Franck, Good frameworks such as GDS solve real enterprise problems. Things like the Hibernate externalizer and the code generation are tools that solve real...
Having problems with message search?
Offline 
Send Email