Unwinding a bit of the Message vs. Message conundrum

to give new API users a proper extension point for their
own messages.


git-svn-id: https://jmonkeyengine.googlecode.com/svn/trunk@7069 75d07b2b-3a1a-0410-a2c5-0572b91ccdca
3.0
PSp..om 14 years ago
parent ec7431e0f1
commit 0fecd032df
  1. 5
      engine/src/networking/com/jme3/network/message/Message.java

@ -42,9 +42,12 @@ import com.jme3.network.serializing.Serializable;
* provide objects with common fields to the other side. * provide objects with common fields to the other side.
* *
* @author Lars Wesselius * @author Lars Wesselius
* @deprecated Message implementations should extend {@linke com.jme3.network.AbstractMessage}
* instead or use the {@linke com.jme3.network.Message} for referencing.
*/ */
@Deprecated
@Serializable() @Serializable()
public class Message implements com.jme3.network.Message { public class Message extends com.jme3.network.AbstractMessage {
// The connector this message is meant for. // The connector this message is meant for.
private transient Client connector; private transient Client connector;
private transient Connection connection; private transient Connection connection;

Loading…
Cancel
Save