On Jun 27, 2006, at 12:49 AM, patrickdlogan wrote: > > I'd prefer > > > > customers = srv.findCollectionByMemberType( "Customer" ) > > customers.add( bobBundyObj ) > > This seems to map onto the Atom Publishing Protocol directly. See how nice this has suddenly become? :-) Just by remodeling the stuff to HTTP's uniform interface there is suddenly a customers feed that you can subsribe to with your newsreader (given we take up with the extra effort to serve application/atom+xml).
Wanna built an event based queuing system on top of that feed? What about another collection besides /customers, e.g. /customers/new where only added customers are placed in...look at it as a sort of customer addition event and have machine news readers subscribe to it to react on new customer events. Suddenly the future is wide open....without *ANY* additional API clutter. I seriously cannot see any reason why I ever should prefer srv.AddCustomer(). Jan > > The first statement would be replaced by a "GET url" where the url is > for an "introspection document" which describes where collections are > located. (Those collections may be on the same server or some other, > it doesn't matter since the urls for the collections are in the > document.) > > The second statement would be replaced by a POST to the "customers" > collection of a representation of the Bob Bundy customer entity. > > -Patrick > > > ------------------------ Yahoo! Groups Sponsor --------------------~--> See what's inside the new Yahoo! Groups email. http://us.click.yahoo.com/2pRQfA/bOaOAA/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/
