commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebb (JIRA)" <>
Subject [jira] Resolved: (NET-344) Telnet client: Support Listener Notification of Incoming Data
Date Thu, 03 Mar 2011 20:58:38 GMT


Sebb resolved NET-344.

    Resolution: Fixed

Thanks, patch applied with minor modifications (e.g. removed @Override from
otherwise it does not compile with Java 1.5)

In future, please provide patches relative to the project root. Thanks.

> Telnet client: Support Listener Notification of Incoming Data
> -------------------------------------------------------------
>                 Key: NET-344
>                 URL:
>             Project: Commons Net
>          Issue Type: New Feature
>          Components: Telnet
>    Affects Versions: 2.0
>            Reporter: Archie Cobbs
>         Attachments: NET-344_updated.txt, combined_NET-343_NET-344_NET-345_patch.txt,
> I am in the process of trying to implement a Java client for [RFC 2217|],
which is the protocol for accessing serial ports over TCP. Unfortunately, the commons-net
telnet client is insufficient for this relatively simple task.
> There are two missing features in the commons-net telnet client code, one of which is
a show stopper (NET-343) and the other of which would be a "real nice to have". This issue
documents the second problem:
> The API I am trying to support requires the ability to notify a listener that new incoming
data is available. This would be trivial for me to do if only my library could somehow itself
get a listener notification from the {{TelnetInputStream}} reader thread every time it reads
new data. Unfortunately, there's no API provided for doing this, even though it would be trivial.
So I have to implement a hack that requires a wrapper {{InputStream}} with yet another internal
reader thread, etc. Bleh.
> I'm going to attempt to come up with a patch and will attach it here if successful.

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message