On 7/15/06, Anne Thomas Manes <[EMAIL PROTECTED]> wrote: > > > Not quite the same -- The central design unit of the naked object pattern > is an object, not a resource.
FWIW, "resource" and "object" are synonymous. Roy Fielding considered using "object" in his work on REST, but found it confused people so stuck with resource (sorry, can't find the reference to his email on this). > A naked object will have getter and setter method for each of its attributes, > and it will expose as many other domain-specific methods as the designer > deems appropriate. For example, you could have an "order" object, which might > expose methods such as addItem, submitOrder, checkOrderStatus, etc. > > The fundamental premise of REST is the uniform interface. No such constraint > exists for the naked object pattern. Right. Mark. ------------------------ Yahoo! Groups Sponsor --------------------~--> Great things are happening at Yahoo! Groups. See the new email design. http://us.click.yahoo.com/TISQkA/hOaOAA/yQLSAA/NhFolB/TM --------------------------------------------------------------------~-> 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/
