Curtis L. Olson wrote:
First, let me point out the new telnet server is *very* nice. Bernie
has rewritten it based on the plib net libs. It can handle multiple
concurrent connections. This is a big improvement!
I'm not sure why you would need to run two or more sessions but there
you go.
Bernie Bright writes:
Curtis L. Olson wrote:
First, let me point out the new telnet server is *very* nice. Bernie
has rewritten it based on the plib net libs. It can handle multiple
concurrent connections. This is a big improvement!
I'm not sure why you would need to run two or
Curtis L. Olson wrote:
[snip]
Bernie, on the subjects of building additional commands into the
telnet interface, I agree with Melchior. I'd rather not see the
telnet interface being crammed with a bunch of extra commands that
only the telnet interface knows about. I haven't looked at
The new telnet server has really become nice. It's great to be able
to connect more than just once. :-)
But I don't like the new commands:
view set n display view 'n'
view get return current view index
view current return current view index
Why bloat the interface
First, let me point out the new telnet server is *very* nice. Bernie
has rewritten it based on the plib net libs. It can handle multiple
concurrent connections. This is a big improvement!
Along with this, Bernie has also provided a demo python script that
shows how you can use the telnet
