Ah, ok. So, by enabling the lateral cache, when a single node in the cluster loads an object with a key of 1234, it will then serialize that object, and multicast it across the cluster, and all listeners will put the object into their local caches?
This is much different than OSCache which just broadcasts flush commands to other nodes. Currently with the lateral, what is happening with our cache when an update occurs and the object is not able to be fully serialized? Will the the other nodes in the cluster at least mark that key as expired and remove the object from the local caches? Or does the message completely fail? Ian. -----Original Message----- From: Smuts, Aaron [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 31, 2005 5:24 PM To: JCS Users List Subject: RE: Serializing question about JCS in a Lateral Cache config No. The lateral sends objects. It doesn't just issue remove requests by default. I'm not sure the configuration option to issue removes instead of requests is exposed. I will expose it tomorrow if it isn't already. I'm also working on a way to plugin a serializer, so if you wanted to use xstream, which doesn't require that your objects implement serializable, then you could. Aaron
