asp.net - How to associate each user visiting a web app with a separate, temporary process allocated by a service? -
I want to develop a web application using ASP.NET running on IIS.
If a user submits a MAXIMA input command, the back-end code will ask to create a new temporary process to execute an external temporary service from a custom Windows service.
More precisely, the service of one window service to all users, but each user will be associated with a separate, temporary process that is running an external assembly.
Window service on a fixed port is to hear a socket and list of asynchronous socket for communication. Each socket in the list will communicate with a separate, temporary process that runs an external assembly that works as a client socket.
Note: I use a process instead of an application domain because the external assembly is not a batch file (managed assembly).
My questions are:
- How to call windows service with the back codes
- How to affiliate each user is a separate, temporary process?
- If more and more users are working together, how to improve scalability?
- If the user enters the Maxima input command, what is the best way to inform the user about long-running process progress?
The following links give you more information about my project:
Thank you in advance.
You should not use codebind in an MVC app
unmanaged code Scalability is difficult when interfering with. The only wise way to do this is to break the problem.
- When you launch an unmanaged app, it is already processed.
- A service in which multiple work flow is called with a web app? You are describing your service hosted with AppFabric, and you will not have to write it all yourself.
- In relation to scalability, when you deal with unmanaged processes, you have to limit the number that must be started concurrently to determine optimum on specific hardware, testing and error will be necessary.
- You can only track the progress of the devaluation work if that app specifically provides for it.
- Launching arbitrary unmanaged code from the service is dangerous, because the launch app, by default, (generally taken) permissions of the service
Comments
Post a Comment