Shawn,
I'm late to this discussion. I'm really interested too (as am for all RFC standard servers).
If you can port the SF one then good. If you can convince the SF team to migrate to Phoenix or be compatible with (dual mode), then better.
If you want some really dynamic thinking, consider Beanshell (BSH) as the env on the server side that is instead of say Bash. 100% standard telnet clients on Windows/Mac/Unic etc connect to a Phoenix server that is giving you an execution env that is a textual equivalent to Beanshell's GUI. It should be fairly easy to use beanshell in this way, one your have a telnet compliant transport, i.e. you will not have to fork beanshell. It is a dream to use and adapt for other purposes. I have an adaption in Jesktop and a simple use in EOB.
I kinda think we should resurrect the UserManagement block. JAMES has one, FtpServer does too. We need a general one that all whould use., and remote Telnet or SSH can validate against...
Regards,
- Paul
At one point (although I don't see it now), the Avalon web site mentioned interest in a Telnet server for Phoenix. It also mentioned the telnetd server that is on SourceForge.
I'm curious if that interest was still there and what are the expectations
regarding the server's functionality.
My interest is that I need some Java TELNET server I/O code at my company and am looking into the SF telnetd code.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
