A future endeavor for DataSpaces might be to add a data query API, wherein users can know if data has been put into the DataSpace for a specified bounding box. This could be achieved by setting up an nD array over the entire global domain (as specified in dataspaces.conf) at initial startup. If data comes in, this would be updated -- like "setting a flag" that proves data from a "put" routine has been received and put into the space at a specific BB. The technical details would need to be explored further: for example, which server is responsible for this?
The purpose of this API would be for usage in more advanced locking mechanisms. For example, to avoid sending user back invalid data for the case of lock type 1. Or, allowing application user to check if data has arrived from a certain version (could be useful in an event-triggered analytics-type application).
A future endeavor for DataSpaces might be to add a data query API, wherein users can know if data has been put into the DataSpace for a specified bounding box. This could be achieved by setting up an nD array over the entire global domain (as specified in dataspaces.conf) at initial startup. If data comes in, this would be updated -- like "setting a flag" that proves data from a "put" routine has been received and put into the space at a specific BB. The technical details would need to be explored further: for example, which server is responsible for this?
The purpose of this API would be for usage in more advanced locking mechanisms. For example, to avoid sending user back invalid data for the case of lock type 1. Or, allowing application user to check if data has arrived from a certain version (could be useful in an event-triggered analytics-type application).