32dee3cbaf
more discipline when handling names in our code base. Any user entered name should find its way into a Name object as soon as it comes out of a text field or whatnot, and stay that way until it makes its way into a text field or into a database record (for which String objects are vastly simpler because of JORA magic). Dear God, let me never again make a change this large for the rest of my mortal life. Unfortunately, this means we have to keep an eye out for funny business pretty much everywhere. However, since we will absolutely want to test market stalls and so forth on Azure, we'll have an opportunity to iron out any funny business that might fall under the radar during our internal testing. git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2980 542714f4-19e9-0310-aa3c-eee0fc999fb1
36 lines
741 B
Java
36 lines
741 B
Java
//
|
|
// $Id: UserMessage.java,v 1.3 2004/03/06 11:29:18 mdb Exp $
|
|
|
|
package com.threerings.crowd.chat.data;
|
|
|
|
import com.threerings.util.Name;
|
|
|
|
/**
|
|
* A ChatMessage representing a message that came from another user.
|
|
*/
|
|
public class UserMessage extends ChatMessage
|
|
{
|
|
/** The user that the message came from. */
|
|
public Name speaker;
|
|
|
|
/** The mode of the message. @see ChatCodes.DEFAULT_MODE */
|
|
public byte mode;
|
|
|
|
/**
|
|
* For unserialization.
|
|
*/
|
|
public UserMessage ()
|
|
{
|
|
}
|
|
|
|
/**
|
|
* Construct a user message.
|
|
*/
|
|
public UserMessage (String message, String bundle, Name speaker, byte mode)
|
|
{
|
|
super(message, bundle);
|
|
this.speaker = speaker;
|
|
this.mode = mode;
|
|
}
|
|
}
|