If the same process is managing the screen and listening on the socket, you'll have some random amount of latency. There's no way around that. There will be times when your socket goes ready that Tk is busy thinking about the screen.

If you need to isolate the latency, put your communication protocol in a second process, and when it has an entire update for the Tk process, it can tap the Tk process on the shoulder and say "here's your new data". I'd do that with two cooperating POE processes (one POE-Tk, one just POE), or maybe an Event.pm loop for the latter.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.