Subj : Re: bbS Servers in Docker
To   : deon
From : paulie420
Date : Sun May 28 2023 19:01:15

 de> I actually used this to get multinode running, so each "node" was a new
 de> window, and VNC enabled me to see what was going on in each window.

Ahhhh - now thats interesting; I didn't think about how you could just open X 
windows w/ jgoerzen's container - that makes it m0re interesting...

 de> Which part? The CPU bit is because DOS thinks it owns the CPU and runs
 de> it full steam. You can load "dosidle" which does give up the CPU, but
 de> when you have a BBS with a WFC screen (or a mailer), it doesnt give up
 de> much :(
 de> 
 de> The mailer part is if you want to use mail transfers (or for that matter
 de> enable file downloads from the DOS BBS). The common transfer being used
 de> (zmodem), is not tollerant to each side of the connection having
 de> different speeds.
 de> 
 de> Since DOS BBSes only talk serial ports - the "DOS" side is limited by
 de> the speed of the emulated serial port - say 115200 baud, but the other
 de> side is ethernet (with operating system buffers). So when a transfer is
 de> done, 1 side waits for the other to say "I'm finished, or I got it" -
 de> and it only waits so long. If it doesnt get a response then it
 de> "timesout".
 de> 
 de> The problem is, for example, the ethernet side sends a file, it fills up
 de> a TCP/IP buffer and it thinks the otherside should have got it (and
 de> waits for the ACK) - but the other side is draining the TCP buffer
 de> through a slow link (115200) and if it takes too long to get to the end
 de> of the buffer, the other side has given up and gone.

Thanks for taking the time to outline/explain some bumps you've hit... I 
appreciate knowing a few things to l00k out for - I'll share if and when I get 
anywhere or hit roadblocks. :P



|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A48 (Linux/64)
 * Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (1337:3/129)

.