> Isn't it possible to write jboss so that RMI is not used when calls
   > are made inside one JVM? If possible, it would be the greatest speed
   > improvement. RMI should be used when neccessary; but when
   > servlet container and EJB server share the same JVM and the same
   > address space...
   > 
   > What do you say ?

   This is precisely what the JBoss+EmbeddedTomcat integration provides. To
   be precise, the integration allows two things:
   * no network usage
   * no parameter copying

   We still use the RMI interfaces (e.g. RemoteExceptions), but the two
   above things are optimized. The second is of course optional since it
   breaks RMI semantics.


Skipping the copying isn't breaking RMI semantics for an argument
(or return value) that is known to be immutable. The obvious
example is String since those can be quite large.

Maybe it is also a good idea to define a Immutable interface that
can be implemented to signal it is safe to skip copying of instances
of a specific class?

Of course it is not much help if the checking takes more time than
the copying :-)  (the memory and gc load created by copying should
be counted in addition to the copying itself though)

      _
Mats Lofkvist
[EMAIL PROTECTED]

Reply via email to