rapi_fmt_tspec(3) Library Functions Manual rapi_fmt_tspec(3)NAME
rapi_fmt_tspec - Format an RSVP tspec
LIBRARY
RAPI Library (librsvp.so, librsvp.a)
SYNOPSIS
#include <rapi.h>
void rapi_fmt_tspec( rapi_tspec_t *tspecp, char *buffer, int length);
PARAMETERS
Points to an RSVP tspec. Points to a buffer that is to contain the formatted tspec. Specifies the length, in bytes, of the buffer that is
to contain the formatted tspec.
DESCRIPTION
The rapi_fmt_tspec() routine reads a given RSVP API (RAPI) Tspec and formats it into a fixed length buffer whose address is specified by
buffer and whose size is specified by length. If the buffer size is too small, the formatted Tspec is truncated.
RELATED INFORMATION
Functions: rapi_event_rtn_t(3), rapi_fmt_adspec(3), rapi_fmt_filtspec(3), rapi_fmt_flowspec(3).
Network: RSVP(7). delim off
rapi_fmt_tspec(3)
Check Out this Related Man Page
rapi_dispatch(3) Library Functions Manual rapi_dispatch(3)NAME
rapi_dispatch - Dispatch an Resource ReSerVation Protocol (RSVP) API event
LIBRARY
RAPI Library (librsvp.so, librsvp.a)
SYNOPSIS
#include <rapi.h>
int rapi_dispatch();
DESCRIPTION
An application calls the rapi_dispatch() routine whenever a read event is signaled on the file descriptor returned by the rapi_getfd() rou-
tine. You can call the rapi_dispatch() routine at any time, but it has no effect unless there is a pending event associated with the UNIX
pipe.
NOTES
When an application calls this routine, the application might receive one or more upcalls from any of the open API sessions known to this
instance of the library.
RETURN VALUES
Upon successful completion, the rapi_dispatch() routine returns a value of 0 (zero). Upon failure, it returns an RAPI error code.
RELATED INFORMATION
Functions: rapi_event_rtn_t(3), rapi_getfd(3), rapi_release(3), rapi_reserve(3), rapi_sender(3), rapi_session(3), rapi_strerror(3),
rapi_version(3).
Network: RSVP(7). delim off
rapi_dispatch(3)
Hi Folks,
Today hasn't been the best one of my career in IT.
I've been a contractor for a major utility company for a number of years, on a number of seperate IT contracts mostly Unix. The company had 10 different flavours of unix and multiple different varsions of most of them.
At the... (3 Replies)