irods  4.2.8
About: iRODS (the integrated Rule Oriented Data System) is a distributed data-management system for creating data grids, digital libraries, persistent archives, and real-time data systems.
  Fossies Dox: irods-4.2.8.tar.gz  ("unofficial" and yet experimental doxygen-generated source code documentation)  

Collaboration diagram for Server Data Transfer Operations:

Functions

int rcDataCopy (rcComm_t *conn, dataCopyInp_t *dataCopyInp)
 
int rcDataGet (rcComm_t *conn, dataOprInp_t *dataGetInp, portalOprOut_t **portalOprOut)
 
int rcDataPut (rcComm_t *conn, dataOprInp_t *dataPutInp, portalOprOut_t **portalOprOut)
 
int rcL3FileGetSingleBuf (rcComm_t *conn, int l1descInx, bytesBuf_t *dataObjOutBBuf)
 
int rcL3FilePutSingleBuf (rcComm_t *conn, int l1descInx, bytesBuf_t *dataObjInBBuf)
 

Detailed Description

Function Documentation

◆ rcDataCopy()

rcDataCopy ( rcComm_t conn,
dataCopyInp_t dataCopyInp 
)
Description:\n Copies data from source to target.
Primary User:\n client
Since
1.0
Remarks
none
Note
none
Parameters
[in]conn- A rcComm_t connection handle to the server.
[in]dataCopyInp
Returns
integer
Return values
0on success.
Side Effect:\n none
Precondition
none
Postcondition
none
See also
none

Definition at line 35 of file rcDataCopy.cpp.

References DATA_COPY_AN, NULL, procApiRequest(), and irods.pypyodbc::status.

Referenced by remoteDataCopy().

Here is the call graph for this function:

◆ rcDataGet()

rcDataGet ( rcComm_t conn,
dataOprInp_t dataGetInp,
portalOprOut_t **  portalOprOut 
)
Description:\n Gets a dataObject on the server.
Primary User:\n client
Since
1.0
Remarks
none
Note
none
Parameters
[in]conn- A rcComm_t connection handle to the server.
[in]dataGetInp
[out]portalOprOut
Returns
integer
Return values
0on success.
Side Effect:\n none
Precondition
none
Postcondition
none
See also
none

Definition at line 36 of file rcDataGet.cpp.

References DATA_GET_AN, NULL, procApiRequest(), and irods.pypyodbc::status.

Referenced by remoteDataGet().

Here is the call graph for this function:

◆ rcDataPut()

rcDataPut ( rcComm_t conn,
dataOprInp_t dataPutInp,
portalOprOut_t **  portalOprOut 
)
Description:\n Gets a dataObject on the server.
Primary User:\n client
Since
1.0
Remarks
none
Note
none
Parameters
[in]conn- A rcComm_t connection handle to the server.
[in]dataPutInp
[out]portalOprOut
Returns
integer
Return values
0on success.
Side Effect:\n none
Precondition
none
Postcondition
none
See also
none

Definition at line 36 of file rcDataPut.cpp.

References DATA_PUT_AN, NULL, procApiRequest(), and irods.pypyodbc::status.

Referenced by remoteDataPut().

Here is the call graph for this function:

◆ rcL3FileGetSingleBuf()

rcL3FileGetSingleBuf ( rcComm_t conn,
int  l1descInx,
bytesBuf_t dataObjOutBBuf 
)
Description:\n Remote call for cross zone single buffer get.
Primary User:\n client
Since
1.0
Remarks
none
Note
none
Parameters
[in]conn- A rcComm_t connection handle to the server.
[in]l1descInx
[out]dataObjOutBBuf
Returns
integer
Return values
0on success.
Side Effect:\n none
Precondition
none
Postcondition
none
See also
none

Definition at line 33 of file rcL3FileGetSingleBuf.cpp.

References L3_FILE_GET_SINGLE_BUF_AN, NULL, procApiRequest(), and irods.pypyodbc::status.

Referenced by rsL3FileGetSingleBuf().

Here is the call graph for this function:

◆ rcL3FilePutSingleBuf()

rcL3FilePutSingleBuf ( rcComm_t conn,
int  l1descInx,
bytesBuf_t dataObjInBBuf 
)
Description:\n Remote call for cross zone single buffer put.
Primary User:\n client
Since
1.0
Remarks
none
Note
none
Parameters
[in]conn- A rcComm_t connection handle to the server.
[in]l1descInx
[out]dataObjInBBuf
Returns
integer
Return values
0on success.
Side Effect:\n none
Precondition
none
Postcondition
none
See also
none

Definition at line 33 of file rcL3FilePutSingleBuf.cpp.

References L3_FILE_PUT_SINGLE_BUF_AN, NULL, procApiRequest(), and irods.pypyodbc::status.

Referenced by rsL3FilePutSingleBuf().

Here is the call graph for this function: