Re: Background Processes - best practice
Re: Background Processes - best practice
- Subject: Re: Background Processes - best practice
- From: Chuck Hill <email@hidden>
- Date: Thu, 17 Jan 2008 21:12:27 -0800
Hi George,
On Jan 17, 2008, at 5:28 PM, George Wiles wrote:
A best-practice question from a WebObjects newbie, any help would
be greatly appreciated.
We have a number of background processes that we need to run to
compliment our WebObjects web application.
What is the WebObjects way of doing this...or [should we stick to
what we know best] and use a J2EE servlet container (eg. Tomcat,
JRun etc) to run our background processes.
What do your background processes do? That is an important
consideration. Mine usually access the database and / or some other
frameworks related to WO. Because of that, I want the power of WO
and I run them in the context of a WO app. In most cases this is an
application for which only a single instance is deployed. Each of
the processes is run in an daemon java.lang.Thread. The app can
provide a useful dashboard as to the status etc of each thread.
Depending on what they do, you might want to have each have its own
EOF stack to avoid threads blocking each other.
Does that help at all?
Chuck
--
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden