>Our flagship GemStone/Smalltalk server provides a totally
transparent
>client/server partitioning capability. One's object model can be
transparently
>replicated to the client, and changes to objects are flushed to the
server
>automatically.
Beautiful! IMHO that's the best load-balancing mechanism yet, and
probably superior to standard EJB servers. I see much value in
client-side
session beans, but migrating entities does seem risky: entities
contain
private corporate data, and optimal entity deployment requires
locality
especially for (JDBC) connection pooling and perhaps other
scalability issues.
But yes, let's consider pushing sessions to the client.
Yes beautiful from a developers perspective, but did you read the rest?
Ulitimately
this capability led to mant Bad implementations...
-Chris.
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
