Hi VOSpronauts:
Quoting Dave Morris <dave-at-ast.cam.ac.uk>:
> If the transfer only involves two spaces, then a direct transfer would
> probably work.
> However, the next stages in the VOSpace road map are to add containers
> and inter-space links which will link the separate space services and
> make them behave as one unified space.
Hm, simple is not complicated enough it seems :^) The fact that there is already a way of supporting cross server operations (copy, move) with the existing methods was meant to show an option to keep implementation effort low. A specification should not disallow certain operations on the grounds that it won't be sophisticated enough to also cope with future requirements.
> As Mark has suggested, the reason for splitting the results into a
> series of pages is to enable the system to handle large numbers of files
> without overloading the server or client.
The incentive of my suggestions is to maintain simplicity by focusing on some usability issues. For instance, if the specification 'allows' to filter list output then this is a way to avoid such an overload. Dave's and Paul's latest postings seem to confirm that we anyway agree on this particular list functionality.
Greetings,
Markus
Received on 2006-08-16Z19:15:54