Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!sdd.hp.com!decwrl!sgi!shinobu!odin!speaker!coolidge
From: coolidge@speaker.sgi.com (Don Coolidge)
Newsgroups: comp.sys.hp
Subject: Re: HP3000 Sockets ?
Summary: HP3000->sockets Works (Relatively) Painlessly
Keywords: NetIPC, sockets
Message-ID: <1990Aug16.221305.18886@odin.corp.sgi.com>
Date: 16 Aug 90 22:13:05 GMT
References: <1990Aug12.234727.8281@portia.Stanford.EDU>
Sender: news@odin.corp.sgi.com (Net News)
Reply-To: coolidge@speaker.wpd.sgi.com (Don Coolidge)
Organization: Silicon Graphics Inc., Mtn. View, CA
Lines: 30

In article <1990Aug12.234727.8281@portia.Stanford.EDU> glowell@portia.Stanford.EDU (gary lowell) writes:
>Hello - 
>
>I would like to use sockets to talk between MPE XL and HP-UX.  My
>SE told me that this could be done with NetIPC on the MPE XL side,  
>and ordinary sockets on the HP-UX side.  I'm trying to avoid HP's
>NS protcol as the Unix side may not always be HP-UX.

Well, NS isn't a protocol - it's HP's proprietary Network Services 
applications (RFT, or dscopy, and RFA, or netunam) using NetIPC for 
an API. What actually communicates are the peer entities - IP<->IP,
TCP<->TCP, and application<->application. An application running over
NetIPC (say, FTP) can talk perfectly well with its peer running over 
sockets, as long as they both have a TCP/IP stack in the kernel. That's
the case for the HP3000 MPE operating systems, so a NetIPC-using 
application on a 3000 can talk to its peer application on any un*x box
(subject to the usual intervendor compatibility warts). So you can
write your NetIPC-using application with no fear of being stuck with
something other than HP-UX on the other side. It shouldn't be too hard;
the system calls are (mostly) quite similar.

Besides, since NetIPC is the _only_ API on a 3000, you don't have any choice.

>Thanks,
>Gary Lowell   
>glowell@portia.stanford.edu
>(415) 369-2303

Don Coolidge
coolidge@speaker.wpd.sgi.com