Comments on: Who needs XPath fragment-level PUT?

By: William Vambenepe’s blog » Blog Archive » Cloud computing: would you like flexibility with your simplicity?

Fri, 20 Mar 2009 08:47:01 +0000

[...] using REST, the Sun team has kept away some arbitrary complexity (e.g. fine-grained PUT; instead Sun decides what are the two valid sets of input parameters to create a cluster). But [...]

By: Bookmarks about Xpath

Bookmarks about Xpath — Wed, 07 Jan 2009 18:30:13 +0000

[...] – bookmarked by 6 members originally found by lmdelgado on 2008-12-20 Who needs XPath fragment-level PUT? http://stage.vambenepe.com/archives/224 – bookmarked by 1 members originally found by lmmvirago on [...]

By: William Vambenepe’s blog » Blog Archive » CMIS, APP, Zen-SOAP and WS-KitchenSink: some data points

Thu, 11 Sep 2008 08:23:29 +0000

[...] “who needs XPath fragment-level PUT?”, I tried to make the case that the use of XPath in WS-RT to do fine-grained updates is a case of [...]

By: William Vambenepe’s blog » Blog Archive » WS Resource Access at W3C: the good, the bad and the ugly

Thu, 10 Jul 2008 07:59:33 +0000

[...] The bad is the whole “resource access” spin. It is not actually intrinsically bad. There are scenarios where such a pattern actually fits. But the way that pattern is being addressed by WS-RT and friends is overly generalized and overly XML-centric. By the latter I mean that it takes XML from an agreed-upon on-the-wire interchange format to an implicit metamodel (e.g. it assumes not just that you agree to exchange XML-formated data but that your model and your business logic are organized and implemented around an XML representation of the domain, which is a much more constraining requirement). I could go on and on about this, especially the use of XPath in the PUT operation. In fact I did go on and on with it, but I spun that off as a separate entry. [...]