EsotericSoftware / kryonet

TCP/UDP client/server library for Java, based on Kryo
BSD 3-Clause "New" or "Revised" License
1.82k stars 419 forks source link

Listener.received sees FrameworkMessage.KeepAlive messages #32

Closed ghost closed 10 years ago

ghost commented 10 years ago

From pie...@spotify.com on January 21, 2013 02:28:47

What steps will reproduce the problem?

  1. Create a client, add a listener with received(Connection connection, Object o) that logs o.getClass().toString()
  2. Connect to a server, stay idle
  3. See FrameworkMessage.KeepAlive messages What is the expected output? What do you see instead? I assume those messages should be considered internal to the framework and hidden to the API consumers. What version of the product are you using? On what operating system? http://kryonet.googlecode.com/svn/trunk@132 Please provide any additional information below. Can be tested using the commit 6a8677496f018553c5ef2bceca3df63c4ed48a26 of https://github.com/pcarrier/kryoflood with 2+ clients, and removing the "else if (o instanceof FrameworkMessage.KeepAlive) {}" workaround.

Original issue: http://code.google.com/p/kryonet/issues/detail?id=31

ghost commented 10 years ago

From nathan.s...@gmail.com on February 06, 2013 10:42:01

It doesn't hurt to have these messages come to the listeners. They could be useful in some situations.

Status: WontFix