xpaaccess.3 | xpaaccess.3 | |||
---|---|---|---|---|
skipping to change at line 31 | skipping to change at line 31 | |||
passed to the server as the data transfer request is initiated. If a n | passed to the server as the data transfer request is initiated. If a n | |||
XPA struct is passed to the call, then the persistent connections ar e | XPA struct is passed to the call, then the persistent connections ar e | |||
updated as described above. Otherwise, temporary connections are mad e | updated as described above. Otherwise, temporary connections are mad e | |||
to the servers (which will be closed when the call completes). | to the servers (which will be closed when the call completes). | |||
The XPAAccess() routine retrieves names from at most n XPA servers t hat | The XPAAccess() routine retrieves names from at most n XPA servers t hat | |||
match the specified template and that were checked for access using the | match the specified template and that were checked for access using the | |||
specified mode. The return string contains both the class:name and | specified mode. The return string contains both the class:name and | |||
ip:port. If a given server returned an error or the server callback | ip:port. If a given server returned an error or the server callback | |||
sends a message back to the client, then the message will be stored in | sends a message back to the client, then the message will be stored in | |||
the associated element of the messages array. The returned message | the associated element of the messages array. NB: if specified, the | |||
string will be of the form: | name and messages arrays must be of size n or greater. | |||
The returned message string will be of the form: | ||||
XPA$ERROR error-message (class:name ip:port) | XPA$ERROR error-message (class:name ip:port) | |||
Note that names of matching registered access points are always | Note that names of matching registered access points are always | |||
returned but may not be valid; it is not sufficient to assume that t he | returned but may not be valid; it is not sufficient to assume that t he | |||
returned number of access points is the number of valid access point s. | returned number of access points is the number of valid access point s. | |||
Rather, it is essential to check the messages array for error messag es. | Rather, it is essential to check the messages array for error messag es. | |||
Any string in the messages array is an error message and indicated t hat | Any string in the messages array is an error message and indicated t hat | |||
the associated access point is not available. | the associated access point is not available. | |||
skipping to change at line 89 | skipping to change at line 91 | |||
------ -------- -------- ----------- | ------ -------- -------- ----------- | |||
ack true/false true if false, don't wait for ack from server (after callback completes) | ack true/false true if false, don't wait for ack from server (after callback completes) | |||
The ack keyword is not very useful, since the server completes the | The ack keyword is not very useful, since the server completes the | |||
callback in order to return the data anyway. It is here for complet ion | callback in order to return the data anyway. It is here for complet ion | |||
(and perhaps for future usefulness). | (and perhaps for future usefulness). | |||
SEE ALSO | SEE ALSO | |||
See xpa(n) for a list of XPA help pages | See xpa(n) for a list of XPA help pages | |||
version 2.1.8 November 1, 2007 xpaaccess (3) | version 2.1.10 September 1, 2009 xpaaccess (3) | |||
End of changes. 2 change blocks. | ||||
2 lines changed or deleted | 4 lines changed or added | |||
This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ |