Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!lll-crg!styx!twg-ap!amdahl!nsc!oblio!unixprt!monkey
From: monkey@unixprt.UUCP (Monkey Face@unixprt)
Newsgroups: comp.unix.questions
Subject: RFS COTS Interface
Message-ID: <178@unixprt.UUCP>
Date: Mon, 1-Dec-86 01:36:33 EST
Article-I.D.: unixprt.178
Posted: Mon Dec  1 01:36:33 1986
Date-Received: Mon, 1-Dec-86 19:57:28 EST
Organization: Paul Fronbergs Computer, Santa Clara
Lines: 27
Keywords: RFS, System V Release 3.0

I hope that this is the correct place to post this.

Has anyone else noticed that the RFS code in System V Release 3.0
connects to the TLI interface using Connection Oriented Transport
Services (COTS), but it expects a message based interface?  

Since COTS is not a message based interface, unless your transport 
provider is message based (transparent to TLI) then RFS does not 
work when activity gets high enough to cause the COTS stream to
void a 'message like' look.

Protocols like TCP/IP which are also stream oriented can not be used
if what I am assuming is true (and I think it is).

Earlier version of the V.3 alpha/beta tapes included a thing called
NPACK that was between TLI and the transport provider to solve this
problem, but is is not in the release.  And also, in reality the tranport
provider in these cases (when TCP/IP was desired) was really 
NPACK/TCP/IP.  Therefore only interfacing to systems that have an 
NPACK/TCP/IP transport provider.

I have a fix to the RFS code that will allow a true interface to a 
COTS transport provider.

I would especially like to here from the boys/girls at AT&T.

Monkey Face @ unixprt (uni-xperts)