Re: [colorforth] ColorForth and VNC Compatibility

[Samuel Falvo <falvosa@xxxxxxxxx>]

> I wonder if it will be impossible to show his screen, since
> he works so closely to the hardware. :-(

Absolutely not at all.  Here are the things you need to convince Chuck about to
get VNC to work:

1.  Implement TCP -- VNC requires a reliable byte stream.  It'd be easiest to
implement a minimal TCP stack to serve the data directly off his laptop.

2.  Implement a background task that, like the normal screen manager, reads
from the current frame buffer and transmits said data over the VNC channel.

3.  Implement a distribution server that is responsible for distributing the
image to everyone who connects to it, so as to not load down Chuck's laptop.

Note that this might require ColorForth to have four background tasks instead
of three, which would require a recompile of his kernel (as I currently
understand how it works).

> My guess is that it is close to what we used to call a 
> TSR.

They're called "daemons" in Unix, and "services" in Windows, and in true
multitasking environments, there is little need for special hacks like TSRs.

--
Samuel A. Falvo II


__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com

---------------------------------------------------------------------
To unsubscribe, e-mail: colorforth-unsubscribe@xxxxxxxxxxxxxxxxxx
For additional commands, e-mail: colorforth-help@xxxxxxxxxxxxxxxxxx
Main web page - http://www.colorforth.com