The busy attribute on a node

[Matthew Graham]

Hi,

The current text regarding the busy node is a bit buried in the spec. In Sec 3.1, it says: "busy: a boolean flag to indicate that the data associated with the node cannot be accessed. The busy flag is used to indicate that an internal operation is in progress, and the node data is not available." The message schema adds: "A flag to indicate if the node content is available. This will be set to false while the data is being imported, or if the underlying service is busy."

The first issue is that the schema should say: "This will be set to TRUE while the data is being imported." since the node is busy.

The second issue is that this means the VOSpace node featured in a pushToVoSpace or pullToVoSpace operation should have its busy flag set to true whilst the operation is in progress and this is not explicitly stated under these operations. This would then have the consequence that any pullFromVoSpace/pushFromVoSpace operation using such a node should fail.

Can we update the text in VOSpace 2.1 to clarify this?

	Cheers,

	Matthew