virtual qBool PostObject( ProtocolCallContext * pContext, const DataStorePostParam & param, qUnsignedInt64 * dataId, DataStorePostObjectEventListener * eventListener ); virtual qBool PostObject( ProtocolCallContext * pContext, const DataStorePostParam & param, qUnsignedInt64 * dataId, const void * buffer, qBool useInternalBuffer = true ); virtual qBool PostObject( ProtocolCallContext * pContext, const DataStorePostParam & param, qUnsignedInt64 * dataId ); virtual qBool PostObject( ProtocolCallContext * pContext, const qUnsignedInt64 dataId, const DataStorePostParam & param ); virtual qBool PostObject( ProtocolCallContext * pContext, const qVector< std::pair< qUnsignedInt64, DataStorePostParam > > & params, const qBool transactional = true, qVector< qResult > * pResults = NULL ); virtual qBool PostObject( ProtocolCallContext * pContext, const qVector< qUnsignedInt64 > & dataIds, const DataStorePreparePostParam & param, const qBool transactional = true, qVector< qResult > * pResults = NULL );
You must initialize the HTTP library by calling the nn::http::Initialize
function before this function is called. If you call this function, a thread for communication is created regardless of the NEX thread mode. The data to upload is specified by the callback function called from eventListener. The data that is uploaded using this function is stored in a special region of the storage server, separate from the metadata.
You must initialize the HTTP library by calling the nn::http::Initialize
function before this function is called. If you call this function, a thread for communication is created regardless of the NEX thread mode. The data to upload is specified from buffer. The data that is uploaded using this function is stored in a special storage server, separate from the metadata.
If you use this function and upload only the metadata, data is not stored in a special storage server.
This function takes a data ID as an argument. With standard uploads, the server automatically assigns a data ID. However, when this function is used, the client can specify the data ID. For more information, see the Programming Manual. If you use this function and upload only the metadata, data is not stored in a special storage server.
This function takes a data ID as an argument. With standard uploads, the server automatically assigns a data ID. However, when this function is used, the client can specify the data ID. For more information, see the Programming Manual. If you use this function and upload only the metadata, data is not stored in a special storage server.
Up to 100 sets of metadata can be batch-processed. The result of processing each data ID specified in params is returned to pResult in the same order in which it was specified. pResult takes only that specified number of results.
This function takes a data ID as an argument. With standard uploads, the server automatically assigns a data ID. However, when this function is used, the client can specify the data ID. For more information, see the Programming Manual. If you use this function and upload only the metadata, data is not stored in a special storage server.
A single item of metadata can be set to multiple Data IDs. Up to 100 sets of metadata can be batch-processed. The result of processing each data ID specified in dataIds is returned to pResult in the same order in which it was specified. pResult takes only that specified number of results.
CONFIDENTIAL