one of the strikes against dynamic deployment is that it is slower.
also, starting with java
source and then trying to abstract that to ruby, etc. there is no path.
the problem with rmi,
jini, etc. is that they are not language binding nimble.
Niclas Hedhman wrote:
I a trying to catch up on the Etch, and IIUIC the "Java Binding"
involves that there is code generated from the IDL and then compiled
with a Java compiler. IMHO, this sounds like Java RMI in JDK1.1, which
over the years have changed to be "generated for client only" to "no
generation needed" in Java5.
I am a framework developer, and would like to "wrap" Etch under the
hoods, invisible to the user, but the "generated source" makes that a
LOT harder, unless I start "tunneling" high level interface methods
over more generic ones, which is a really, really bad idea. Do you
guys have any plans for more dynamic deployment options?
Cheers
Niclas
