I've had a brief look at the possibility of adding IPv6 support to ToolTalk. It is necessary for me as rpc.ttdbserver when invoked from FreeBSD's inetd will likely receive an AF_INET6 ::1 socket instead of AF_INET 127.0.0.1.
The TI-RPC stack that supports NFSv4 and IPv6 has imported lots of Sun's RPC features and APIs, including <netconfig.h>, clnt_create() and clnt_create_timed() and rpcb_set(). Those functions are also provided by libtirpc for Linux. Those APIs, however are almost not tied to the Transport Layer Inteface (TLI, a.k.a. as XTI) APIs that are System V's approach alternative to BSD sockets (t_accept, t_bind, etc.). Only (struct t_bind) needed for svc_tli_create() is provided. So BSDs and Linux could use new RPC functions on top of the traditional socket stack. What I would propose is to separate OPT_TLI into two options: * OPT_TLI -- if defined then use TLI instead of BSD sockets * * OPT_TLIRPC -- if defined then rpc code is compiled for the new * transport-independent rpc And use OPT_TLI for functions related to sockets only, and introduce OPT_TLIRPC for the new RPC calls. For all systems that had OPT_TLI defined, OPT_TLIRPC should be defined as well. Some more work is needed on: In slib/mp_rpc_server.C - netconfig and svc_tli_create() that are available in the TI-RPC are used, but the socket is created using t_open. - gettransient() should be written a bit differently. - lib/mp/mp_rpc_fns.C should be split _tt_tli_set_nodelay and _tt_bind_endpoint relate to the TLI sockets, while _tt_svc_freeargs and _tt_svc_getargs are related to the TLI RPC. What do you think about splitting OPT_TLI like this? //Marcin ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ cdesktopenv-devel mailing list cdesktopenv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cdesktopenv-devel
