I'm building an application that will allow users to manipulate
real-world systems (routers, in this case) via a web application. But we
can't perform changes in real-time, because:
1. changes can take several minutes to implement
2. the systems may be in use, such that it's not appropriate to make
the change now
So, my app will allow changes to scheduled as "jobs" to be performed
asynchronously ... possibly with a delay until a nominated time.
My prototype stores jobs in a database, and periodically polls for jobs
that are ready to go. But there's got to be a better way!
I'm thinking of something like an EJB Session Bean that implements the
scheduling engine. But I'm going to need something with it's own thread
of control, in order to trigger jobs that are ready to be processed ...
EJBs can't have threads associated with them, can they? Can anyone
recommend a suitable model using EJBs?
cheers,
Mike
===========================================================================
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".
