RE: Creating a subsystem

>I'm working on the packaging of a software application. This app is the
>server side of a client/server system. It is a single, multi-threaded,
>never-ending program that will be submitting secondary long-running,
>resource-intensive jobs.
>
>My initial reaction is that we should create our own subsystem to run
>everything in. However, I don't really know how clients feel 
>about that.

We let our customers make those decisions.  Instead of requiring them to
start a subsystem named xxx, we suggest it (for easy troubleshooting).
Things like job queue names and libraries go into configuration files so the
customer can set things up the way they need.

One major consideration is that you want to allow the customer to have
multiple copies of this thing running: one test environment and one
production, for instance.
  --buck