> From: A mailing list for Enterprise JavaBeans development
> [mailto:[EMAIL PROTECTED]]On Behalf Of Ben Strulo
> However, it is not clear to me that these two solutions [smartkeys vs entity
> beans] are really comparable from a performance point of view. In the smart
> key case the references are held on the client. Thus the storage demand on
> the server is constant as the number of clients increases. In the entity
> bean case the server is maintaining some kind of entity-bean instance table
> (mapping references) and this will use storage linear in the number of
> concurrent clients and hence damage scalability (certainly in extreme
> cases).
In theory, you are right. In practice, servers are typically clustered. In this
scenario, maintaining the keys in clients is extremely complex. Better leave this
up to the servers, who know about each other and can inform each other as keys are
created, deleted or updated.
--
Cedric
===========================================================================
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".
