From: D-Man <ds...@ri...> - 2001-07-20 15:43:54
|
On Fri, Jul 20, 2001 at 08:02:12AM +0000, Paul Giotta wrote: | | I am currently have a side project that will do something like this. It | is a module that implements a telnet daemon that runs as a java thread. | When someone connects, it starts a jython interpreter and uses this as | the shell for user interaction. Thus, if this is embedded in a running | server, you can connect using an ordinary telnet client and manipulate | object running in the same VM. This is still work in progress, but some | of the sticky points so far: | | - Implementing telnet: I tried to find a java telnet daemon that I | could adapt or borrow code from. There does not seem to be any yet. Also | getting complete and understandable documentation for the telnet protocol | is not that easy (every time I use a new telnet client, it starts trying | to negotiate some other connection parameter that i cannot find in any | documentation). You should probably just ignore anything not mentioned in the RFC. All you need is character input, output, and (ideally) backspace. This is all the interactive interpreter provides anyways (no readline in Java :-( ). If you don't do anything then the telnet client should behave properly (I think). What I mean is, for example, try "telnet mail 25" and see how telnet can connection to an SMTP server just fine. You could also try that on port 80 and see how HTTP daemons have no trouble with it either. A telnet client should be able to connect to any port and behave, though it might not have any advanced terminal features. -D |