Re: Editorial section 9.3: updating

[James M Snell <jasnell@xxxxxxxxx>]

It's not a replace.  The server determines how to modify the resource
based on what the client gives it.

For instance,

If I have an entry:

  <entry>
    <id>urn:foo</id>
    <title>Foo</title>
    <updated>2007-12-12T12:12:12Z</updated>
    <summary>Bar</summary>
    <author><name>James</name></author>
    <link href="http://example.com/blog/2007/12/foo"; />
  </entry>

And I PUT the following:


  <entry>
    <id>urn:foo</id>
    <title>Bar</title>
    <updated>2007-13-13T13:13:13Z</updated>
    <summary type="html">&lt;b&gt;Foo&lt;/b&gt;</summary>
    <author><name>Bob</name></author>
    <link href="http://example.com/blog/2007/13/foo"; />
  </entry>

Different APP servers are going to have completely different responses.
 Some may just pick up the change to the title and summary, ignoring all
of the other changes.  Some may replace the entire entry.  Some may
reject the new entry entirely because they might not support HTML
summaries.

The resource is not being replaced.  It is being modified.

PUT in APP is not Replace.

- James

Keith Fahlgren wrote:
> [snip]
> Having just read your blog entry on the same, I think "replace" makes
> the most sense to me.
> 
> 
> HTH,
> Keith
> 
>