W3C home > Mailing lists > Public > ietf-dav-versioning@w3.org > January to March 2002

Philosophical: Batch processing

From: Kirmse, Daniel <daniel.kirmse@sap.com>
Date: Wed, 13 Feb 2002 13:52:27 +0100
Message-ID: <59357A260E15D311B5A60008C75D3530068B47D5@dbwdfx13.wdf.sap-ag.de>
To: "Ietf-Dav-Versioning (E-mail)" <ietf-dav-versioning@w3.org>
Hi,

I have a philosophical question dealing with batch processing in DeltaV. Is
it right to suppose that batch processing functionality must be provided by
the client? 
Well lets take an example. Merging a workspace (containing a complete
codeline) into another workspace may be a huge task to fullfill. Typically
such tasks/jobs would be startet in batch mode. So a client could or would
have to provide a scheduler that is the tool for scheduling batch jobs.
Problem is that the server would reply instantly when the request is
completely performed. The client would have to store the replies to provide
them as soon as they are requested.
This is definitly a way to it. But what about this MERGE above? Typically
the reply contains failed merges that have to be handled somehow. Performing
such a MERGE would raise failures that different developers have to handle.
So a central batch processing support would be a nice thing. Anyway you
still could have an administrator client that provides batch processing and
messaging of failures to the developer responsible.

Does anyone has experiences with this topic? Oppinons?

Regards,
Daniel
Received on Wednesday, 13 February 2002 07:53:15 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 13:57:43 GMT