Sorry to jump in so late on this thread...

On Fri, Jul 17, 2009 at 11:32 AM, Tim Peierls<> wrote:
> Some rambling newbie Restlet design questions:
> Background: I'm in the preliminary stages of a ground-up redesign of an
> existing non-Restlet application. I'm (naturally) convinced that Restlet is
> the way to go for this redesign, and I'm pretty sure I want the UI to be
> GWT-based. So far so good ... GWT-Restlet is alive and well. (And I'll get
> cracking on a Restlet-Guice extension before too long, or not, depending on
> how you define "too".)
> My analysis of the existing application keeps leading me to the Atom
> Publishing Protocol, because the key elements of that application "feel"
> like collections of publishable/updatable resources (and collections of such
> collections). It doesn't fit the canonical examples of APP, however, which
> leads to my first questions: Does anyone know of APP being used successfully
> outside of the usual document/news item examples that everyone uses to
> explain it? If so, what criteria would you use to determine whether APP is
> really appropriate to my resource design?

I use the APP for all kinds of applications.  I use it as a basic storage
and retrieval mechanism.  Of course, I use a lot of advanced features
found inside Atomojo for querying feeds and that is most certainly
outside of the APP as a protocol.

> I'm sort of hoping the answer is a resounding yes to this, in which case my
> second question is: If I want to design my application around APP but I
> don't intend to use a file-based storage system like eXist, what does
> Atomojo have for me that the Restlet Atom extension doesn't? Is there
> something else that I should know about?

I think you are a bit confused about what Atomojo has to offer.  First of all,
there is a server that supports the APP and provides different storage
mechanisms.  There are currently two storage mechanisms: files and the
eXist XML database.  I've considered writing an Amazon S3 storage
back end but I haven't quite gotten to it yet.  Basically, storage is something
that you can change in the server.

The server itself maintains an index and supports different kinds of
metadata and query services independent of the storage used.  You can
use these services to build applications--which is what I do.

Atomojo also provides:

   * a Java client for interacting with the APP
   * a Javascript client for doing the same
   * a web server component that uses configures itself using
     atom feeds (a special wrap-up of Restlet)
   * some other application components for building
     web applications.

Much of this still needs documentation.  :(

--Alex Milowski


Reply via email to