On 25/07/14 17:44, Mark Feblowitz wrote:
I use the latter - separate submissions of a single update request containing
several statements :
INSERT DATA { ...
...
...
} ;
So it seems that I could consider buffering up a number of these within the
same update request.
Out of curiosity, does an update request get submitted to the server as one
“payload” and processed at the server, or is the set broken down into
individual INSERT DATA requests that are sent across the wire? Or as individual
INSERT DATA requests, one per statement (one per “…”)?
ARQ does not add any buffering internally - one DatasetAccessor or one
UpdateProcessor.execute is one HTTP request.
What would be the scope of the transaction? Per update request or per INSERT
DATA?
HTTP Request (= update request).
How are transaction failures reported?
HTTP response codes
(note that there aren't any system generated aborts so failures are due
to bad input (400) or system bugs (500))
Andy
Thanks,
Mark
