Re: Serialised applets using the Sun Plug-in

Thomas Hawtin wrote:


I don't know about others, but I have to admit..
they are new to me.

...What is that actual point of serialising applets?

A quick bit of googling led me to these possible
advantages ..
 - can encapsulate applet
    1) binary,
    2) resources,
    3) state *and*
    4) parameters.
 - ..that's it really. (is there something I missed?)

So it seems to come down to 'encapsulation'
(If not, I'm about to stray off into irrelevance.)

The first and second of the above can be achieved
by rejarring the classes with the resources (crude,
but should work).

I cannot see the point in storing the state of
the applet (I *could* as far as the end user
goes, assuming it could save their 'current work',
but what is the advantage to the deployer?).

Encapsulating the parameters of the original applet
is a little trickier, and might involve either extending
the target applet and overiding init(), or putting it
inside another applet that supplies a custom applet
context that you can configure (by whatever means).

Thoughts?

Andrew T.