Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!srhqla!nrcvax!bvs
From: bvs@NRC.COM (Bill Versteeg)
Newsgroups: comp.protocols.tcp-ip
Subject: inter-machine socket interface
Message-ID: <444@nrcvax.NRC.COM>
Date: 21 Dec 89 03:22:23 GMT
Reply-To: bvs@nrc.COM (Bill Versteeg)
Organization: Network Research Corp., Oxnard CA
Lines: 35



I am in the process of designing a system where an application
living in one box (without a tcp/ip stack) needs to use a tcp/ip
stack living in another box. The connection is via a serial line.
The machine running the applications can't run a full stack, it
is not a big enough box.

I have a proprietary protocol that extends a pseudo-socket interface
into a "smart-card" card environment. This protocol assumes
a shared memory architecture. ( In other words telnet, ftp, etc live
in a xenix context, while tcp/ip live in a smart card).

Is there a standard method of running a "socket" interface over 
a light weight transport layer so that it can utilize the TCP services
of a co-operating system? I don't know of any, so I am about
to embark on a project to extend our proprietary software interface
to not require a shared memory environment. If there has been any work
done in this area, I would love to hear about it.

Otherwise, I will have to do to the socket layer interface what has been
done to IP in PPP. In fact, I believe I will use what I can of PPP.

This is a rather weird request for work done in a pretty specific
area, so rather than clutter up the net, please respond to me directly.

Bill VerSteeg
Network Research Corp.
bvs@nrc.com

-- 
Bill VerSteeg
Network Research Corporation
1000 Kristian Way			
Roswell Ga. 30076					bvs@nrc.com