My point was that if we are going to be object-oriented on the web, we need to
really be object oriented, and that means that we *must* move code
around. Java shows us one way of doing this, but it is hardly the only way;
but any way has to be both portable and secure. This is not, by the way, the
party line...while applets are like this, most other Java APIs don't make use
of the dynamic and mobile nature of Java. Right now, the Web is object
oriented in a clumsy way, moving around indications of what code is needed
(generally via Mime types) but requiring the code to be moved by hand. The
point I was trying to make is that we need to find a way of allowing the code
to be moved as easily as the data if we really want to have objects on the web
(and, by the way, we really do want to have objects on the web).
But I guess I wasn't clear enough about this. Sigh...