Hello Bita, Yes, those classes would go into those packages. The Batch method in the server part would instantiate the requested batched methods (e.g. a series of deletes).
For the request I would use "...\jakarta-slide\testsuite\testsuite\junit\Tprocessor.dtd" as a starting point: <!ELEMENT request (command, header*, body?)> Why not use <!ELEMENT request (command, header*, body?)> as the response, in this case a multiple get would be possible too. Binary data is currently read via the fileReference element, in your case you would need to define how binary data would be transported within an utf-8 encoded XML document. Best regards, Juergen -----Original Message----- From: Bita Shadgar [mailto:[EMAIL PROTECTED]] Sent: Monday, February 25, 2002 14.11 PM To: Slide Users List Subject: Re: Batch methods "Pill, Juergen" wrote: > Hello Bita, > > Did you follow the discussion on topic "Interest in standardizing Batch > methods?" in the WebDAV discussion list [EMAIL PROTECTED] Yes. > > > A BATCH implementation would be a non standard extension, but helpful. I > believe implementing a batch method would be not too difficult (in Side). > May I would suggest an architecture? > > The client would be added a new BATCH method transporting an XML document, > which contains the nested WebDAV method in a string format. Possibly the > (modified) DTD of the test cases could be a good starting point. The DTD > could contain an additional element, specifying if all commands would be > executed within a single transaction. > > The server would be added a new BATCH method, which parsers the XML > document, depending on the flag starts a TA and invokes the necessary server > WebDAV methods. The request/response data-structures need to be simulated. > Based on them the response document would be generated (a nested > multi-status document?). > > Would you be interested in designing the batch method semantics and the > implementation in Slide (client/server) > Yes, I would. Since in my project I need to put or delete a bunch of files, I prefer to have a batch method rather than many usual methods which take a lot time of system just to transfer data over the internet. Indeed, Thanks for your points and as I understand I need to add a class like Batch.java in the client part ( webdav/client/org/apache/slide/webdav/method/) to create an xml request and also a class in server side (/webdav/server/org/apache/slide/webdav/method/ ) to parse and execute method, am I right? However, at present I have no idea about which format should be preferred for an xml batch request and response as well. Do you have any idea? > > Best regards > > Juergen Thanks for all your help, Bita. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
