>
> RPM does make for efficient communications on the HP3000 however -- my fear
> is that one day, if it does happen, it will go by the wayside and become
> obsolete.  Heck, the full NS product is practically obsolete now with inetd
> and telnet.  It's fast and reliable, but proprietary.  In this
> internetworked world, sockets library implementation seems to be the better
> way to go.  (I will say this - speaking only from QEDIT for Windows though,
> as I cannot speak for Whisper - maybe Jaime can offer the answer) -- I can
> use QEDIT over the Internet, as was demonstrated last year at IPROF - we
> edited some files over a dial-up connection to a local ISP - these files
> were on one of our 3000s in Pennsylvania (editing files from 3200 miles away
> was nice to show).
>

Joe,

Programmer Studio uses TCP/IP to connect to the server.

We have several clients who connect to their HP3000 over the internet
for editing.   Most of these clients go thru firewalls as well.

On a side note I have found that porting the server daemon to other
platforms, e.g. Linux/SCO/HPUX, the real bug-bear was actually trying to
figure out how to validate and "become" a different user.   So although
the sockets implementation was "standard" this was (almost but not
quite) totally different on each platform.

What one hardware platform giveth, another hardware platform taketh ;)



Jamie.