On Wed, Nov 28, 2001 at 12:32:53PM +0000, Stephen Watson wrote:
> In message <20011128121031.A19509@...>
> Thomas Leonard <tal00r@...> scribbled:
> > On Wed, Nov 28, 2001 at 11:27:35AM +0000, Stephen Watson wrote:
> > > I've been looking at the --RPC option. Would it be useful to add
> > > Copy/Move/Link to the available commands, so that you could do e.g.
> > >
> > Certainly. We just need to change the last few actions that take
> > FilerWindow arguments (instead of pathname lists).
> It would also be useful to have functions such as action_copy_with_options so
> that you can do <Copy quiet="yes" force="no">.
> Then create some Python and C functions that handle the nuts and bolts of
> creating the XML and sending it to rox -R. They could go in ROX-Lib.
> I should have something working in a couple of days, depending on free time.
Cool. To get at the filer interface via ROX-Lib we need another property
on the root window to find the filer by name, host and user (but not
version). Allowing ROX-Lib to control the filer directly should speed
things up a bit, too...
BTW, don't use attributes on the RPC call to pass parameters; it's not in
the SOAP spec. It should be something like <Copy><quiet>1</quiet>...</Copy>
[ we slightly extend the SOAP spec by allowing multiple method calls in
one SOAP message, but that should be OK -- it only makes a difference
when an invalid SOAP RPC is sent ]
The filer also doesn't (yet) deal with SOAP replies. Although most of the
code is there, none of the methods actually return anything...
Thomas Leonard http://rox.sourceforge.net