edu.stanford.hci.r3.actions.remote
Class ActionJavaObjectXMLMessenger
java.lang.Object
edu.stanford.hci.r3.actions.remote.ActionMessenger
edu.stanford.hci.r3.actions.remote.ActionJavaObjectXMLMessenger
public class ActionJavaObjectXMLMessenger
- extends ActionMessenger
Sends an R3 Action as a Java object serialized to xml over a socket.
TODO: Seems like we could integrate this with PenServer's equivalent classes. How do we make it
generic so that we can send an object over and either consider it a pen sample, or an action?
Might be simpler to keep them separate for now. There are some issues with the way we serialize
(removing spaces, et cetera).
This software is distributed under the BSD License.
Method Summary |
byte[] |
getMessage(R3Action action)
Turns an R3Action into an xml string and then into the bytes we need to send. |
Methods inherited from class java.lang.Object |
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
ActionJavaObjectXMLMessenger
public ActionJavaObjectXMLMessenger(java.net.Socket s)
- Parameters:
s
-
getMessage
public byte[] getMessage(R3Action action)
- Turns an R3Action into an xml string and then into the bytes we need to send.
- Specified by:
getMessage
in class ActionMessenger
- Returns:
- See Also:
ActionMessenger.getMessage(edu.stanford.hci.r3.actions.R3Action)