On Sun, 2002-07-21 at 12:29, Hanson Char wrote: > Actually this idea won't work, as there are many objects that don't make > sense at all if we serialize/deserialize them - eg io stream objects, > connections, etc.
And leaving the interface as taking Objects allows us the possibility of caching these objects. (I mean if the implementations were modified to allow it.) I am ambivalent. I like compile time checking as well and since none of the underlying implementations do accept un-Serializable objects it would make sense to use Serializable in the interface(s). Is everyone else of the opinion that it is not worth keeping the option to cache non-Serializable objects open? john mcnally -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
