Also, not knowing whether you're going to get pass-by-reference or pass-by-value semantics could lead to a lot of coding issues. Imagine a shopping cart stateful session that has a method that returns its contents as a vector. If the return is by reference, the client could change the internal state of the bean behind its back. If bean developers have no way of specifying the semantic of an operation, things could get messy in a hurry.

-danch

Tom Gardner wrote:
"Bill Burke" <[EMAIL PROTECTED]> wrote in
news:[EMAIL PROTECTED]:


I hope all this Remote and Local crap is removed in 3.0.  There really
is no reason for it.


It is Monday, so I disagree.

From a logical point-of-view you are, of course, correct.

From an operational point-of-view your position is less
tenable....


In high performance latency-sensitive applications written by large teams and maintained over periods of years, it is advantageous to be able to specify and verify (perferably by the compiler) that certain accesses cannot unwittingly become remote.

In high-availability applications, it is also necessary
to understand and deal with partial failure stories. If
objects cannot be remote then this problem becomes trivial :)





------------------------------------------------------- This SF.Net email is sponsored by: INetU Attention Web Developers & Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to