Re: WS-Fragment uploaded

The end semantics are the same though - the only difference between the 
two are syntax.  Frag is just an on the wire optimization. 

thanks
-Doug
______________________________________________________
STSM |  Standards Architect  |  IBM Software Group
(919) 254-6905  |  IBM 444-6905  |  dug@us.ibm.com
The more I'm around some people, the more I like my dog.



Yves Lafon <ylafon@w3.org> 
09/29/2009 09:48 AM

To
Doug Davis/Raleigh/IBM@IBMUS
cc
David Snelling <David.Snelling@UK.Fujitsu.com>, 
public-ws-resource-access@w3.org
Subject
Re: WS-Fragment uploaded






On Tue, 29 Sep 2009, Doug Davis wrote:

> Nope - both are updating am existing resource.  Slightly different
> instructions for how to do it, but its still updating an existing
> resource.
> But it this way...ignoring frag, if I have a resource of the form:
> <foo/>
> and I do a T.Put() with:
> <foo>
>  <bar/>
> </foo>
> did I just do a T.Create()?  No, I updated an existing resource.  The 
fact
> that in the process I inserted a new element has no impact the fact that
> I'm still doing an Update/Put. All that's different with frag is that 
I'm
> using a less verbose syntax to do it.

Without frag, you did send <foo><bar/</foo> not <bar/> with instruction to 

create a subnode of <foo/>

When you are doing a FragPut@mode=Insert on <foo/> of <bar> it's like 
doing a Frag.Create of <bar/> in <foo/>, and both are different from a Put 

with <foo><bar/></foo>


-- 
Baroula que barouleras, au tiéu toujou t'entourneras.

         ~~Yves