[DAS] [Fwd: Re: Writeback implementation]

[Andy Jenkinson]

Gregg Helt wrote:
> On Fri, Oct 31, 2008 at 7:22 AM, Andy Jenkinson <andy.jenkinson at gmail.com>wrote:
> 
>> I can't find a description of the response to a writeback command in Asia's
>> thesis. Does it contain features (as in DAS2) or just a confirmation?
> 
> 
>  Take a look at the writeback spec (
> http://biodas.org/documents/das2/das2_writeback.html ), it's much shorter
> than the retrieval spec, just a few pages.
> 
> The general idea is that a server may not be able to do all the
> creations/edits/deletes a client is requesting in exactly the same form the
> client has specified, and furthermore that changes a client requests in one
> feature can possibly trigger changes in other features.  Therefore the
> semantics of the client request are "here's what I want to do" and the
> writeback server responds with "here's what I actually did".  In the DAS2
> writeback spec these are communicated mostly by passing back and forth
> feature XML, except for deletion getting it's own special bit of XML.

I looked at the DAS2 spec, but I was wondering specifically about Asia's 
implementation - whether it did the same or returned either a simple 
confirmation or a DAS 1.53 features response.