home *** CD-ROM | disk | FTP | other *** search
- Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
- Path: sparky!uunet!spool.mu.edu!wupost!howland.reston.ans.net!paladin.american.edu!auvm!CC1.KULEUVEN.AC.BE!SYSTHVU
- Organization: K.U.Leuven (Belgium)
- Approved-By: Herman Van Uytven <SYSTHVU@CC1.KULEUVEN.AC.BE>
- Message-ID: <NETNWS-L%93010808012567@VM1.NODAK.EDU>
- Newsgroups: bit.listserv.netnws-l
- Date: Fri, 8 Jan 1993 14:52:02 +0100
- Sender: NETNWS-L Netnews List <NETNWS-L@NDSUVM1.BITNET>
- From: Herman Van Uytven <SYSTHVU@cc1.kuleuven.ac.be>
- Subject: REXTCPIP versus RXSOCKET (was NNR installation)
- Lines: 19
-
- REXTCPIP uses a VMCF interface to the TCPIP machine, while RXSOCKET
- uses IUCV. RXSOCKET is only usable if you have version 2 of IBM's
- TCP/IP.
-
- We use REXTCPIP in our NNTPXMIT (which is a client to send news),
- and we use RXSOCKET in our NNTP (which is a server to receive news
- and to support reading/posting of news). We didn't have any problems
- with REXTCPIP or RXSOCKET so far.
-
- REXTCPIP is easier to understand/program, but we couldn't succeed in
- using REXTCPIP for a server which need to handle multiple simultaneous
- connections (it is possible, but then you have in fact a CPU loop).
-
- REXTCPIP is available form VM-UTIL carrying listservers, RXSOCKET
- is on listserv@pucc.
-
- For NNR it doesn't make any difference which one you use.
-
- -Herman-
-