Hey
Imre Kifor wrote:
> Which platforms could be affected? Standard CORBA platforms (since they
> don't have GC at all) and standard JDK1.1 platforms (they don't have
> adequate GC). Should the EJB spec be expanded to fix this behavior? No, IMHO
> the EJB architecture is sound and is highly scalable. Paired with the Java 2
> platform, that implements adequate DGC and "weak" references(coincidence?),
> the above problem is not exhibited.
What do you refer to here? I too have been in the dark as to just how
RMI/IIOP based EJB-server was supposed to handle this. A comment from
Vlada hinted that RMI/IIOP will have "persistent" references, which in
my mind could only be that the client stub uses the primary key as
object identifier, hence allowing the server to intercept and reactivate
inactivated entity EJBObjects.
What do you mean with "adequate DGC in Java2"? And how do weak
references come into play, since they're VM-local?
Thanks!
/Rickard
--
Rickard �berg
Computer Science student@LiTH
@home: +46 13 177937
Email: [EMAIL PROTECTED]
Homepage: http://www-und.ida.liu.se/~ricob684
===========================================================================
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".
