For a new web application project using .NET, an existing library (written in C#) will be made available online which performs some calculations on information in a data model.
The library needs to be accessed by many users at the same time. Every user will work with a different set of data. Users also can modify model data and repeat the calculation with modified input parameters.
Currently, the library can only handle one data model at a time. (Let’s assume there are design issues like static classes and singletons).
If a .NET web application (a simple web frontend using HTML web pages) wants to use this library, is there a technology available to create a separate instance of the library for every client, to keep the models and other parameters separated?
You could load the module externally and create a new instance every time or use object pooling by use of .NET Enterprise Services (COM+), but if the object is stateful, you are still going to have scalability problems.
Per comment: Yes, you can. Check out this example, for a quickstart.