From: Alexandre Oliva (oliva@dcc.unicamp.br)
Date: Tue Feb 09 1999 - 19:19:10 EST
On Feb 9, 1999, Tim Wilkinson <tim@transvirtual.com> wrote:
> The downside is that every readObject/writeObject operation
> requires the inner class to be created (and they're very short lived) -
> ah well say I.
This could be easily worked around by making the inner class static
and passing the object as an argument. But there's another bad side
of your approach: it will be much slower for private fields, because
an accessor method will be used to access them.
> The serialization systemlooks for the inner class and uses that if
> it finds it, otherwise it just falls back on the default mechanism.
I'd rather look for alternate implementations only for non-default
serialization mechanisms, and use the default
readObjectState/writeObjectState methods for the default serialization
mechanism.
--
Alexandre Oliva http://www.dcc.unicamp.br/~oliva aoliva@{acm.org}
oliva@{dcc.unicamp.br,gnu.org,egcs.cygnus.com,samba.org}
Universidade Estadual de Campinas, SP, Brasil
This archive was generated by hypermail 2b29 : Sat Sep 23 2000 - 19:58:02 EDT