sigonasr2/jmonkeyengine
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Unwinding a bit of the Message vs. Message conundrum

Browse Source 
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
This commit is contained in:
PSp..om 2011-03-21 23:34:13 +00:00
parent ec7431e0f1
commit 0fecd032df
1 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
engine/src/networking/com/jme3/network/message/Message.java
View File

@ -42,9 +42,12 @@ import com.jme3.network.serializing.Serializable;
* provide objects with common fields to the other side.
*
* @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()
public class Message implements com.jme3.network.Message {
public class Message extends com.jme3.network.AbstractMessage {
// The connector this message is meant for.
private transient Client connector;
private transient Connection connection;