Design Suggestion on webapp using executable windows Web Service client

Question

We have existing web application that needs to interface with a web service through a client exe file.
Inputs will be passed by xml file and output files generated after.
This client exe has configuration file, among the important items on this file is the settings on where the output files will be created.
I personally think this design is wrong but I will have to work through it because I am in no position to change the proposed solution.
A synchronized method for the complete cycle of the call to this method will not be acceptable due to bottle neck issue.
I'm planning to make a singleton class to provide the services for this this client.
I'm planning to get the client IP to use for making temporary working folder for each user.
File IO on creation of input file will be surrounded in a synchronized block.
Runtime.exec call will also be wrapped in a synchronized block.
I will be executing this single exe on seperate process each call,
As for the config file, I will have to edit the config file for each call, since i cannot discern the output files if I put them in single location.
/sigh
Advise would be greatly appreciated.

Answer 1

DarrylBurke wrote:
Seifer wrote:
Someone please tell me I'm doomed?If you say so.
You're doomed.
db
Note: That's a joke, I don't have any knowledge on the specifics of your question.I thought so. I figured one workaround, maintain multiple copies of the client exe, each with their own config referring to each unique output folder and make a pool manager to manage these babies.
I still think the better solution is to give away this client and have the webapp interact directly to the web service. The present kind of remind me how cgi process are used in the old times to serve web requests.