Services and Daemons
If you are familiar with WorldServer and the various processes, you may realize that not every requested job is scheduled for immediate execution or that while it might be scheduled, it does not complete prior to restoring control back to the caller. For example, when you create a new project in WorldServer, it does not execute the project before returning the UI control back over to the user. Instead, it queues the project to be executed. Similarly, you may be familiar with the WorldServer garbage collection processes. These are scheduled to run at specific times, particularly at times when users are less likely to be using the system. The garbage collection process will perform tasks such as cleaning up expired sessions from the database, deleting old asset caches from the database, and performing statistics on the database.
Both the garbage collection and workflow (project execution) processes require specialized daemons to be running in order for these requests to be fulfilled. These daemons are started up with the installed WorldServer instances. Currently, these processes cannot be run in conjunction with a stand-alone SDK application.