This is the Java API for the Light Weight Event System.

***
Prerequisites
- JDK 1.5.x (http://java.sun.com/)
- Maven 2.2.x (http://apache.maven.org/)

***
How to build:
% mvn clean package

To create a release:
% mvn --batch-mode release:prepare release:perform

***
To increase the read buffer size on the multicast socket, set the system property
MulticastReceiveBufferSize. For example,

java -DMulticastReceiveBufferSize=8388608 ...

***
1.0.0 Changes
- Spec: https://github.com/lwes/lwes-website/blob/master/specs/lwes-v1
- ip_addr is now deprecated and should not be used. Use a byte array or a string for ip addresses.
- New data types: byte, float, double
- Array support
- Required/Optional
- Size limitations

***
0.2.5
Changed license to BSD.

***
0.2.4
- There is a memory leak in jdk 1.6.0_20 and earlier in
java.util.concurrent.LinkedBlockingQueue so I made a copy of that class and
fixed the memory leak.

***
0.2.3
- Allow one to override the size check that is done as part of the Event class. Size
really only matters if one is intending on emitting the created event not if they
are reading it from a file. Also allow introspection into Event to get the size in
bytes.

***
0.2.1 -> 0.2.2 Changes
- Added the ability to set a maximum capacity on the internal queue used by the
ThreadedProcessor. If you set the queue size, you can avoid out of memory exceptions,
but you run the risk of dropping events on the floor (it would depend on how fast
you are processing events and how big your network buffer is).

***
0.1.1 -> 0.2.0 Changes
- I removed the files that are autogenerated by javacc and made it part of the build.
The .java files will end up in target/generated-sources/javacc if you are interested in
seeing them.

- I also nuked the ant build.xml file. I don't want to support both ant and maven and imo,
maven wins. :)

- Added more unit tests

- Allow post event creation validation

- Use LinkedBlockingQueues where possible to retain event order and help synchronization.

- I removed AttributeNotSetException because throwing an exception if an attribute isn't set
in the event should not be the proper behavior (after all, HashMap and the like do not do this).