> This is certainly a difference between REST and Naked Objects.
REST/HTTP is a way to exchange representations of objects across the
network based on operations-in-the-large.
Naked Objects is a way to generate user interfaces that manipulate
objects, with less hand-written code, based on some specification of
the object's operations-in-the-small.
I could imagine an application ("rich" client, AJAX, SWT, whatever)
being based on Naked Objects, allowing the human to manipulate objects
at a fine grain with less programmer effort. When those changes need
to be exchanged with another system, the updated representations could
be transferred using PUT, the new objects could be transferred using
POST, deleted objects using DELETE, etc.
-Patrick
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/service-orientated-architecture/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
