I am in the process of building a service that wraps a legacy application using 
a RESTful (JSON based) interface. I need to serve concurrent users, and my 
application can only serve one user at a time. I have to start up to n 
instances of my legacy application. My application takes a while to startup and 
it is stateful.

I can write a configuration driven system that starts the legacy application on 
different nodes, perform lifecycle management, and request dispatching. 
However, I was wondering whether there was anything in the Globus Toolkit in 
terms of code or design inspiration that I should take into account before I 
start?

I know the question is vague, but I am trying to get a handle on the problem 
and I quite haven't done that yet.

Thanks,

Saj

Reply via email to