telnetd2 Open source embeddable telnet daemon written 100% in Java
Download

telnetd2 Ranking & Summary

telnetd2 Tags

manage daemon telnet connection manager telnet connection telnet daemon

telnetd2 Description

Open source embeddable telnet daemon written 100% in Java telnetd is an open source and free Java telnet daemon that is compact and generic and thus easily embeddable into other applications. Here are some key features of "telnetd2": · Telnet protocol implementation (following specifications, support for NVT, ECHO, TTYPE, NAWS, LINEMODE,NEWENV) · Terminal I/O with support for various terminal types · Simple UI toolkit as OO layer on top of the basic terminal I/O (work progress) · Connection management (host based access and handling of idle connections) Requirements: · Java 5 or later What's New in This Release: · Added support for forceBold() and terminal side linewrapping negotiation. (wimpi) · Added complete support for telnet environment option. (wimpi) · Switched to Forrest (0.6) for project documentation generation. (wimpi) · Code is now using the Collections API, Vectors and Hashtables have been replaced with List and Map implementations (ArrayList and HashMap). All use of Enumeration instances has been transformed into using Iterator instances. (wimpi) · Thread handling has been updated to conform with post Java 2 specifications. There are no yield() calls any longer and no calls to the deprecated stop() (which was declared to be inherently unsafe). This implied that there is no broken connection handling any longer. All I/O Exceptions are bubbled up to the application level shell and I/O implementations, and have to be handled properly (instead of the CONNECTION_BROKEN event). (wimpi) · Start and stop methods have been adjusted, the proxy now only accepts the unified properties file at startup and the daemon plus all configured listeners need to be started using: m_Daemon = TelnetD.createTelnetD(m_Properties); m_Daemon.start(); (wimpi) · Complete logging has been switched to the commons-logging wrapper and is using log4j at the moment (that's default anyway). Applications should use the initialization mechanism of log4j on startup or initialize log4j accordingly (on startup is done by passing a system property through the jvm e.g. -Dlog4j.configuration=file:///log4j.properties). (wimpi) · ConnectionQueue has been completely removed from the codebase. (wimpi) · Documentation has been updated to reflect all telnetd2 changes. (wimpi)

telnetd2 Related Software