libt2n 0.4 (Default branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News libt2n 0.4 (Default branch)
# 1  
Old 09-27-2008
libt2n 0.4 (Default branch)

libt2n is a C++ library for inter-process communication (IPC) or remote procedure-calls (RPC). It comes with an additional code generator (libt2n-codegen) to generate stubs and skeletons. The focus lies on a minimum of code lines needed to export and use methods, and being able to use complex C++ structures like maps of vectors. License: GNU Lesser General Public License (LGPL) Changes:
This release adds Client-Wrappers; see examples-codegen/example1-client-wrapper for how to use them. It has an API-incompatible change: command_client now takes a client_connection pointer instead of a reference. Building of documentation for "out of tree" builds has been fixed. A bug with nested namespaces has been fixed. A bug with incomplete writes has been fixed. This release provides access to buffer/block sizes of the socket handler. The documentation has been updated. Image

Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question
rpc_xdr(3)						     Library Functions Manual							rpc_xdr(3)

NAME
rpc_xdr, xdr_accepted_reply, xdr_authunix_parms, xdr_callhdr, xdr_callmsg, xdr_opaque_auth, xdr_rejected_reply, xdr_replymsg - XDR library routines for ONC remote procedure calls SYNOPSIS
#include <rpc/xdr.h> xdr_accepted_reply( XDR *xdrs, struct accepted_reply *ar); xdr_authunix_parms( XDR *xdrs, struct authunix_parms *aupp); void xdr_callhdr( XDR *xdrs, struct rpc_msg *chdr); xdr_callmsg( XDR *xdrs, struct rpc_msg *cmsg); xdr_opaque_auth( XDR *xdrs, struct opaque_auth *ap); xdr_rejected_reply( XDR *xdrs, struct rejected_reply *rr); xdr_replymsg( XDR *xdrs, struct rpc_msg *rmsg); DESCRIPTION
These routines allow C programs to make procedure calls on other machines across the network. First, the client calls a procedure to send a data packet to the server. Upon receipt of the packet, the server calls a dispatch routine to perform the requested service, and then sends back a reply. Finally, the procedure call returns to the client. Unless otherwise indicated, the routines described in this reference page are thread safe (that is, they can be used safely in a multi- threaded environment). Routines that are not thread safe are flagged as such. Encodes RPC reply messages. This routine is useful for users who wish to generate RPC-style messages without using the RPC package. Describes UNIX credentials. This routine is useful for users who wish to generate these credentials without using the RPC authentication package. Describes RPC call header messages. This routine is useful for users who wish to generate RPC-style messages without using the RPC package. Describes RPC call messages. This routine is use- ful for users who wish to generate RPC-style messages without using the RPC package. Describes RPC authentication information messages. This routine is useful for users who wish to generate RPC-style messages without using the RPC package. Describes RPC reply messages. This routine is useful for users who want to generate RPC-style messages without using the RPC package. Describes RPC reply messages. This routine is useful for users who want to generate RPC-style messages without using the RPC package. RELATED INFORMATION
rpc_clnt(3), rpc_misc(3), rpc_svc(3), xdr(3) Remote Procedure Calls: Protocol Specifications - RFC 1050 delim off rpc_xdr(3)