Skip to content
Snippets Groups Projects
Deucе's avatar
Deucе authored
It was badly broken, especially with large files... we now don't
try console.write() unless there's enough space in
console.output_buffer_space.

On my system (debug build of Synchronet), the most I can push through
console.write() over telnet is about 1.9MB/s.  My release build of
SyncTERM can consume about 4MB/s of string data, so Synchronet is the
choke point in my setup here. (SSH is much worse)

My super-cool demo thing ends up needing about 90 seconds to preload
all the cache stuff, so it's simply not useable, even locally. :(

If I use client.socket.send(), I can unlock the Synchronet throughput,
but I can't remember if client.socket is the passthru socket with SSH
or not... and there's no way to synchronize the socket with the console
at the end of the send (console has flush(), Socket doesn't, and even if
it did, it wouldn't flush through to the output buffer).
2760bfe1
History

Synchronet Project

BBS-Related Software Source Repository

Directories within:

  • 3rdp - Third-party libraries
  • ctrl - Synchronet BBS configuration and run-time data files
  • docs - Synchronet BBS documentation (mostly legacy HTML)
  • exec - Synchronet BBS executable files (mostly JavaScript)
  • install - Synchronet BBS installation files
  • node1 - Synchronet BBS Terminal Server "node" configuration files
  • src - Source code (mostly C/C++)
  • text - Synchronet BBS text and menu files
  • web - Synchronet Legacy/Runemaster web UI
  • webv4 - echicken's web interface (v4) for Synchronet
  • xtrn - Synchronet BBS doors (mostly JavaScript)

Related web-sites:
Synchronet BBS Software
Synchronet Wiki
Synchronet Source Repository