"split" is interpreted by rxgen to produce two client interface routines: StartRXAFS_StoreData and EndRXAFS_StoreData.
The whole RPC looks then like StartRXAFS_StoreData(); rx_write(); ... rx_write(); EndRXAFS_StoreData(); That means the data of the file are transfered without additional xdr-overhead just as a byte-stream. Hartmut "Neulinger, Nathan" wrote: > > When I see: > > StoreData( > IN AFSFid *Fid, > AFSStoreStatus *InStatus, > afs_uint32 Pos, > afs_uint32 Length, > afs_uint32 FileLength, > OUT AFSFetchStatus *OutStatus, > AFSVolSync *Sync > ) split = 133; > > What is the split indicating? I'm trying to improve the afs dissection in > ethereal. It looks like the initial packet has the in values, but 2nd and > further packets do not have any of those values. Except, there is no > reference in that function description to the actual 'data' that is being > stored. Is that what split indicates? That there is additional blob data > tacked onto the end of the request, possibly multiple packets long? > > -- Nathan > > ------------------------------------------------------------ > Nathan Neulinger EMail: [EMAIL PROTECTED] > University of Missouri - Rolla Phone: (573) 341-4841 > Computing Services Fax: (573) 341-4216 > _______________________________________________ > OpenAFS-devel mailing list > [EMAIL PROTECTED] > https://lists.openafs.org/mailman/listinfo/openafs-devel -- ----------------------------------------------------------------- Hartmut Reuter e-mail [EMAIL PROTECTED] phone +49-89-3299-1328 RZG (Rechenzentrum Garching) fax +49-89-3299-1301 Computing Center of the Max-Planck-Gesellschaft (MPG) and the Institut fuer Plasmaphysik (IPP) ----------------------------------------------------------------- _______________________________________________ OpenAFS-devel mailing list [EMAIL PROTECTED] https://lists.openafs.org/mailman/listinfo/openafs-devel
