Jean-Sebastien Delfino wrote:
Dan Becker wrote:
One item that has been published in the Tuscany future roadmap
(http://tuscany.apache.org/sca-java-roadmap.html) is the need for Atom
binding etag and server sided caching support. JIRA TUSCANY-2447 has
been opened to track this feature.
I think it would be useful to:
1) build a scenario to help us explore what the app developer needs to
write (like Luciano's photo gallery or a simple customer info data base
for example)
2) study and compare how others (popular REST APIs, ATOM implementations
and content management systems) expose etags / if-modified to
application developers.
Thanks for the guidance Sebastien. Now, a few questions for the
developer group.
1) At this point my implementation is based on the Apache Abdera
project, similar to the Tuscany binding-atom-abdera modules. Does anyone
have any issue with updating the POM to the Abdera 0.4 (2008-04-11)
level? I need the update for some of the new framework features. Any
hard requirements for the older Abdera 0.3 (2007-10-05) level?
2) Do people have a preference for entity tag support for Tuscany based
on abstract classes or mix-in helper classes? The former style tends to
make it easy to extend a base collection type, overwrite a method or
two, and run. The latter style tends to give more flexibility, but then
also requires that the collection writer know the base APIs and how to
use them. Any thoughts appreciated.
--
Thanks, Dan Becker
