Why not use JMS to push request and thus create multiple events that are asynchronous
and supported by the EJB container. Your multi-thread monitor could receive JMS
request and instantiated any resources needed.
-----Original Message-----
From: Chris Raber [mailto:[EMAIL PROTECTED]]
Sent: Thursday, October 21, 1999 9:41 AM
To: [EMAIL PROTECTED]
Subject: Re: Monitoring state
As mentioned in previous posts, the client to the EJB's can be
multi-threaded (assuming that the client itself is not an EJB... as pointed
out by Ian). So you could have a multi-threaded "monitor" that talks to the
beans its monitoring on a scheduled basis. An EJB server that lets you chose
how various services are activated an co-located would be advantageous.
I'd be careful with polling based protocol here if you need to scale this
up! You might also want your beans to push events to the monitor when
certain state changes occur, and use polling as a stop gap when events
aren't received within a time band.
Once again we see we need to mix the EJB model with other models that are
asynchronous for certain applications.
-Chris.
----------------------------------------------------------------------
Chris Raber, Director Professional Services, GemStone Systems Inc.
100 West Big Beaver, Suite 200, Troy, MI 48084
phone: (248)-680-6691, fax: (248)-680-6689,
email: [EMAIL PROTECTED]
web: http://www.gemstone.com/
----------------------------------------------------------------------
===========================================================================
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".
