Incorporate a list of classes which are banned from serialization (such as
Thread objects). Throw an informative exception early in the serialization
process when such an object is encountered.
This is to fix issue 6, where a somewhat vague exception is thrown, stating
"buffer limit exceeded", when an object to be sent indirectly holds a reference
a Thread object.
Original issue reported on code.google.com by ni...@npgall.com on 19 Nov 2012 at 10:42
Original issue reported on code.google.com by
ni...@npgall.com
on 19 Nov 2012 at 10:42