Just to get a feel for it, I used ICOMM for a short while. It worked as a
graphic web browser from a shell account. However, it did its dirty-work by
sending commands to the shell, so it put a considerable burden on the host. As
a result, it wasn't popular with the free shell account providers of the early
'90's. I'm thinking that the way Icomm worked, the host computer's IP
stack is
what was doing the work.
Dick
----- Original Message -----
From: "Christopher Smith" <csmith(a)amdocs.com>
To: <classiccmp(a)classiccmp.org>
Sent: Wednesday, November 21, 2001 8:44 AM
Subject: RE: OT: paging MAC expert(s) --- What's a Performa?
-----Original
Message-----
From: Iggy Drougge [mailto:optimus@canit.se]
What kind of bollocks is that? How do you expect
to run a web
browser without
a TCP/IP stack? I suppose you wouldn't fancy Netscape on the
Mac any more,
since you had to buy MacTCP in order to run that.
But then again, what browser doesn't require a TCP/IP stack
in order to be
used online?
I believe there was at least one MS-DOS browser that didn't (doesn't)
require a _separate_ stack. That is, since it is built into the browser.
There is also slipknot(slipnot?), which acts as a front-end to a
shell-account with lynx. :) (That's an interesting program...)
Regards,
Chris
Christopher Smith, Perl Developer
Amdocs - Champaign, IL
/usr/bin/perl -e '
print((~"\x95\xc4\xe3"^"Just Another Perl
Hacker.")."\x08!\n");
'