On Fri, 2003-03-28 at 01:43, Andreas Raab wrote:
> Hm ... thinking about this - you could do it on a per-method level if you
> just tell the other side which selectors are implemented. In this case the
> MD could be stubbed out with methods which pull in the appropriate
> implementation and continue from there.
>
Whether you actually gain something here depends on the average size of
classes/method dictionaries and the average size of methods, of course.
Maybe I put the granularity too low with suggesting doing this on a
method-level. Still, it's interesting to know that it could be done
(most things that *can* be done *are* done in Squeak, sooner or later
;-)).

Biggest issue, of course, is security. I refer to RMI class path
annotation hell for an example of how it shouldn't be done...
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20030328/df147a00/attachment.pgp