🚀 go-pugleaf

In <3muwwB4w165w@tcscs.UUCP> tcscs!zeta@src.honeywell.com (Gregory Youngblood) writes:

>mccall@mksol.dseg.ti.com (fred j mccall 575-3539) writes:

>> In <C0Asys.5C0@panix.com> isc@panix.com (David Koosis) writes:
>> 
>> >On a related note:
>> 
>> >hasn't anyone come up with a (ms) windows-based windowing
>> >protocol yet? so that we could run bbs's with windowing
>> >interfaces?
>> 
>> >I've seen America Online's nifty GEOS front-end, as well 
>> >as some X-windows front ends, but nothing for windows.
>> 
>> 
>> >do we have to do it ourselves?
>> 
>> Probably, and I would expect it to be DOG SLOW running over anything
>> less than a V.32bis connection.  Of course, X has this problem, too.

>Look at PCAnywhere from Symantec.  I've not used it personally, but it does
>windowing in VGA.  All it does is send the commands over the phoen system,
>and makes your local system draw the same boxes that are drawn on the remote
>system.  This seems like a good way of doing things.  And it shouldn't be
>as bad as trying to send a lot of picture data.  

However, Windows and X are not that amenable to this sort of thing.
If you want to see what it will look like, try X across a SLIP
connection.  Anything under about 19.2k and most things CRAWL.  Both
Windows and X do a lot of graphic bitmap sorts of things.  Simply
doing windowing isn't that big a deal.  Running something like X or
Windows across a phone line is something else again.  This is why PC
GEOS and things like NAPLPS are relatively fast.

-- 
"Insisting on perfect safety is for people who don't have the balls to live
 in the real world."   -- Mary Shafer, NASA Ames Dryden
------------------------------------------------------------------------------
Fred.McCall@dseg.ti.com - I don't speak for others and they don't speak for me.