Well, we use it for some internal servers that that I've written myself. I wrote my servers in C, and have them reading/writing to stdin/stdout. On the other end I have VB applications talking to them through the Send and Get methods of the Winsock control. They pass messages back and forth using a text API that we defined. It's a rather beautiful harmony of Unix and NT. Dave :) -----Original Message----- From: sfbosch [mailto:sfbosch]On Behalf Of Stephen F. Bosch Sent: Friday, April 14, 2000 1:44 PM To: [EMAIL PROTECTED] Subject: Using tcpserver for other tcp applications Russell Nelson wrote: > ucspi-tcp installs like this: > > tar xfz ucspi-tcp-0.88.tar.gz > make install > > This is NOT rocket science. But still, to answer your question, no, > you can use inetd, but why would you want to bother? inetd is harder > to use than tcpserver, by far. Just trying to wrap my head around > inetd's "You must supply argument 0 for the command as well as the > path to the command unless you use the default path (which varies from > vendor to vendor)" gives me a headache. Just writing it *down* gives > me the shudders. I'd like to use tcpserver for other things, too, like telnet and ftp. Is there an ucspi-tcp mailing list (I found the available docs for them impenetrable - not like the qmail stuff at all)? -Stephen-
