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'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?



Reply via email to