Donald Edgar wrote:
>
> Robert,
>
> perhaps I misinterpreted the nature of the 'transient data' you refer to. I
> usually mark attributes transient if the algorithm is essentially stateless
> and the transient attribute is used to cache intermediate results which may
> (or may not) be of use to other processes. If this is your case (and if your
> EJB implemetation supports this) you could set the bean timeout period long
> preventing the singleton's removal by the server.
>
> Alternatively, you could of course give the singleton persistent state, so
> it wouldn't matter if it were temporarily removed from the server. Which
> method is most suitable for you application will depend on the volume of
> data being cached and the number (and frequency) of clients accessing the
> bean.
>
> Donald.
>
Donald,
OK, there was a misunderstanding on my part. I was indeed
(mis)interpreting 'transient data'
in a different way. Never mind the noise ;-). I was referring to
scenarios where you would have to give the 'transient data' persistent
state to make it work in an EJB environment.
Regards,
Robert
--
(-) Robert Kr�ger
(-) SIGNAL 7 Gesellschaft f�r Informationstechnologie mbH
(-) Br�der-Knau�-Str. 79 - 64285 Darmstadt,
(-) Tel: 06151 665401, Fax: 06151 665373
(-) [EMAIL PROTECTED], www.signal7.de
===========================================================================
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".
