From: Robert Klemme <bob.news@...>
Date: 2004-11-23T00:18:04+09:00
Subject: Re: Blocks, serailizing, and "configure, don't integrate"


Hmmm,

as the writing and reading instance is the same, what about writing a
class that acts as a block proxy and that recreates the code after loading
the way you described but with a single difference: the code is encryptet.
Of course, with reasonable effort it's still easy to play foul - but at
least you can make sure that noone changes serialized code accidentally or
on purpose and then simply loads it.

Another thing in the direction of your mini-language could be this: you
write a class that describes the callback relationship.  Callbacks
typically just forward an event to somewhere (or you can enforce this
rule).  Then the callbacks are generated from the connection information
(source instance, source event, target instance, target method to invoke).

Just my 0.02EUR...

Kind regards

    robert