Cassie wrote: >> Here is a brief outline of the two java options: >> >> 1. Implementation based on abdera. >> Most code is located in the shindig.social.abdera package. >> >> Note: When evaluating look at the PersonJsonAdapter and PersonAdapter >> implementations as they are the most updated. (as opposed to activities and >> appdata) >> >> 2. "DataService" (similar to the old wire format GadgetDataServlet) >> Most code is located in the shindig.social.dataservice package.
I've got both options working in my project's workspace, so here's my two cents. Option #1 is really "Implementation based on Abdera AtomPub Server Framework." Initially, I thought this was the best option because the Abdera server framework takes care of all the little details of AtomPub compliance, Atom format parsing/generation and it is extremely pluggable. Plus, Abdera has a fairly active community that is generally eager to help. Option #2 is DataService, which is a "custom REST framework." Though I initially opposed the idea, I like the option #2 code. It's simple and gets the job done without the crazy-flexible complexity of the Abdrea AtomPub server framework. But don't forget that the Abdera AtomPub Server Framework is only one part of Abdera. The core of Abdera is a high-performance Atom format parser/generator with lots of nice features like incremental parsing, IRI support, etc. Make sure you take a close look at this option before you roll your own Atom format parser and generator for option #2. - Dave
