On Jul 7, 2006, at 11:32 AM, Radovan Janecek wrote: > Yes to all your questions. > > So what I call operation in this case is PUT <setOff/> or PUT > <setOn/>. > > You apparently have one operation PUT <any/>. And you solve the > problem of what to PUT at runtime. > > Radovan >
I think this is somewhat analogous to the JavaBean convention: setName() setAddress() getName() getAddress() have both a shared meaning (get retrieves and is safe, set is (like PUT) idempotent and mutating), as well as a specific meaning (what do they set). Not entirely the same, but somewhat similar - the shared knowledge enables tools such as IDEs to offer some generic functionality, similar to HTTP proxies which could cache the result of GETs. Stefan -- Stefan Tilkov, http://www.innoq.com/blog/st/ ------------------------ 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/
