iddi/oocsi — pull request #1 by sander (2014-09-18 18:08:50+00:00)
Title: Fix OOCSIEvent property and parameter order

Example Processing code:

```java
import nl.tue.id.oocsi.*;
import nl.tue.id.oocsi.client.*;
import nl.tue.id.oocsi.client.protocol.*;

void setup() {
OOCSI recipient = new OOCSI(this, "myrecipient", "localhost");
recipient.subscribe("mychannel");

OOCSIClient sender = new OOCSIClient("mysender");
sender.connect("localhost", 4444);

new OOCSIMessage(sender, "mychannel").data("mykey", "myvalue").send();
}

void handleOOCSIEvent(OOCSIEvent event) {
println(
event.getSender(), // returned timestamp, now returns sender
event.getRecipient(), // returned sender, now returns channel
event.getChannel(), // returned sender, now returns channel
event.getTimestamp()); // didn't exist, now returns timestamp
}
````

It would be useful to have `OOCSIEvent.getRecipient()` actually return the name of the receiving `OOCSICommunicator` rather than the channel on which the event was received. But that's nontrivial, e.g. it may break `OOCSIMessage`, so I'm leaving that to a separate pull request.