🚀 go-pugleaf

> Some thing like this is probably of interest to many.
> Would you please make your re-write of libtsap and
> tsapd using TLI publicly available?
> 
> Making it part of the standard distribution could also
> be a good idea.
> 

Sorry, I'm not allowed to release the code because of conflicts with AT&Ts
upcoming OSI offerings for SVR3/4. However, I can offer the following
advice to anyone attempting to get ISODE working over TLI.

1.	Re-writing libtsap was not that difficult. The documentation
	on libtsap gives a very clear definition. TLI and libtsap are both
	generic transport interfaces and the mapping between the two
	is fairly straightforward, the only exception being the receive
	side of connection establishment (see below).

2.	libtsap and TLI use the terms 'listen' and 'accept' differently.
	i.e. TNetListen does not map to t_listen and TNetAccept does not map
	to t_accept.

3.	The way TLI handles multiple connection requests (i.e. when a
	second connect request arrives on a stream before the first has
	been accepted or rejected) is difficult to handle within libtsap
	especially when forking a process for each request. This can be
	circumvented by modifying tsapd to be a TLI server (see the
	Network Programmers Guide for examples). In fact if you can live
	without static servers (I think quipu is a static server but hasnt
	been ported to SVR3 anyway) it is not necessary to implement
	TNetListen, TNetAccept and TNetFork.

4.	xselect in libcompat also needs modfiying to use poll().

5.	I ran this over the starlan TP4. I used tsels of the form
	"hostname.filestore" for example and let the starlan directory
	server resolve network addresses.

Good luck,

Keith Coulson
AT&T Bell Laboratories
Summit NJ