Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Message-ID: <21158758.205631290201205844.JavaMail.jira@thor>
Date: Fri, 19 Nov 2010 16:13:25 -0500 (EST)
From: "Archie Cobbs (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Subject: [jira] Created: (NET-344) Telnet client: Support Listener
 Notification of Incoming Data
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Telnet client: Support Listener Notification of Incoming Data
-------------------------------------------------------------

                 Key: NET-344
                 URL: https://issues.apache.org/jira/browse/NET-344
             Project: Commons Net
          Issue Type: New Feature
          Components: Telnet
    Affects Versions: 2.0
            Reporter: Archie Cobbs


I am in the process of trying to implement a Java client for [RFC 2217|http://tools.ietf.org/html/rfc2217], 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.
-
You can reply to this email to add a comment to the issue online.