Chuck-
Sounds like a perfect fit for a stateless session bean.
Best Regards,
Randy Stafford
Senior Achitect
GemStone Professional Services
> -----Original Message-----
> From: Chuck Butkus [SMTP:[EMAIL PROTECTED]]
> Sent: Thursday, April 20, 2000 11:21 AM
> To: [EMAIL PROTECTED]
> Subject: Bean Design Question
>
> In our application, we have the need for a component that can be accessed
> by
> multiple clients but that does not need to store its information
> persistently. It needs to have high performance so storing and loading
> to/from persistent storage on a regular basis would not work.
>
> We are looking at using EJB to provide scalability and failover so we
> would
> like to have this object represented as an Enterprise Bean.
>
> The problem is it doesn't seem to fit in either the Session or Entity bean
> category.
>
> Can we use an entity bean that doesn't talk to a database in its
> ejbLoad/ejbStore methods?? How would this affect scalability and
> failover?
> Should this be an enterprise bean at all?
>
> ==========================================================================
> =
> 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".
===========================================================================
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".
