Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!spool.mu.edu!olivea!oliveb!amiga!boing!dale
From: dale@boing.UUCP (Dale Luck)
Newsgroups: comp.dcom.modems
Subject: Re: Netblazer+T2500+NCD+Xremote ?
Keywords: NCD's Xremote, T2500 and Netblazer
Message-ID: <993@boing.UUCP>
Date: 7 Jun 91 15:30:35 GMT
Article-I.D.: boing.993
References: <1991May27.085335.20997@ecrc.de> <98874@lll-winken.LLNL.GOV>
Reply-To: dale@boing.UUCP (Dale Luck)
Organization: Boing, Milpitas, Ca.
Lines: 29

In article <98874@lll-winken.LLNL.GOV> casey@gauss.llnl.gov (Casey Leedom) writes:
>| I'd like to hear from anyone using the Telebit Netblazer plus two
>| T2500's, one local, one remote with an NCD using the Xremote software.
>| Can this work to provide dialup users with X at home or remotely at, say,
>| a trade show, demo etc ?  Any problems you encountered, distances, other
>
>  Urk ...  Uhmmm, I think you have extreme overkill here.  For a single X
>terminal at home, the only real options are either an NCD running their
>Xremote software or a GraphOn.

Async DECnet at 9600 baud works quite well and is tolerable. Compressed
slip suffers from a bit more overhead but it will do as long as you are
running window managers, etc. locally.

Regarding Xremote. Seems to me that Xremote is not a very modular
solution, being a combination application level protocol and transport.

I feel that a significant serial line speed up could be had just be
compressing the application layer data and then feed it to the
transport layer. This way all that is needed is a compressor/decompressor
on each side of the wire and existing servers and clients could be used.
Sort of the way xscope works.

Am I missing some obvious reason why this would not work?


-- 
Dale Luck     GfxBase/Boing, Inc.
{uunet!cbmvax|pyramid}!amiga!boing!dale