Re: Same Question

Jay Arden Ashcraft (
Mon, 24 Jul 1995 11:56:53 -0500 (CDT)

Dorcey said:

: This is not exactly what you describe because when no one else is
:connected, the reflector and sender will still maintain a keep-alive
:"conversation," exchanging a packet (of less than 100 bytes) every 3
:seconds or so. This would seem to be a negligible load on your net, but
:there is the problem that if network service is disrupted, the connection
:would time out, and then it would have to be re-initiated from the desktop
:machine. I can imagine other problems with maintaining a continual
:connection (e.g., limiting machines use for other purposes), so there would
:be value in what you suggest, and something like it will probably become
:part of the protocol.

I have found Timbuktu as an invaluable tool to reconnect the main sender
whenever the network service has problems or when the server goes down.

I can reconnect the main sender from home via 14,400 baud from/to the desktop
at work. Timbuktu and CU-SeeMe work well together in this application.
I usually with system 7.5x double click to close the audio and video
windows to limit the packets from Timbuktu from the main box and remotely
reconnect the main box. I use refmon and monitoring of logs via NCSA
telnet to monitor activity.

P.S. Reflector feedback: I have noticed refmon to report wrong numbers
under the who command with the new 4.00b1 reflector though reporting 65XXX
lurkers or senders at times. Pretty cool watching it throttle though.

Does 4.00b1 in non-multicast throttle to and feed at lowest receiver
speed or send slow to slow clients and fast to fast clients simultaneously?

OSF runs but can't seem to connect to it.

Jay Ashcraft
204 West 44th Street
Austin, TX 78751-3705

512.459.1366 vox
512.471.1576 fax
copyright 1995 all rights reserved
all comments are mine and do not reflect any organization