I initially removed it because the serialversionuid is only useful, from what I understand, in the case where you would be serializing classes and storing them for a long time. The UID could then be used to inform java that much later on after the class has been modified that the stored class can't be deserialized into the newer class definition. This, however, is completely bogus in the cascading case where serialization only happens over a network socket, not to any persistent storage.

That being said, we can add it back in for now and use it as a marker to inform other developers that this class is serializable and include a comment that informs them as to why. The UID is also only useful if we manually increment/change it every time that we modify the class. If we don't do that, I think having this UID is only going to cause problems by tricking java's serialization system into thinking that newer versions of the class should be able to deserialize older stored data.