David Primmer wrote:
[snip] Here are some specific technologies in Abera that might be useful: The internal Abdera Filter system (that works like java servlet filter chaining) as an output filter to allow the json/xml output decision to be made late or early in the processing and standardize the rest of the request processing. After thinking about this, it's probably not going to be applicable, but there may be other uses for Abdera filters.
This can be handled in a couple of ways. Every CollectionAdapter method returns a ResponseContext object that is responsible for serializing the response. Filters can modify the ResponseContext in a variety of ways and the serialization is always done as late as possible.
Shindig can choose to implement Filters that produce the correct output; or, alternatively can choose to implement custom ResponseContext implementations, or can use things like the existing StreamWriterResponseContext object, or any combination of options.
Using the new, fairly experimental RouteManager system that James has ported from rails (makes generating urls much easier) instead of the StructuredTargetResolver.
As a quick note: it is a partial port; not all of the capabilities of the rails route mechanism are supported.
- James
Abdera has an OAuth client. Do we want to add an OAuth server? quick server impl guides: http://cwiki.apache.org/confluence/download/attachments/69763/abderaserverguide.pdf http://cwiki.apache.org/confluence/display/ABDERA/Your+first+AtomPub+Server davep
