Threading Model

[surzycki]

Hello all,

I am going to be creating and Intranet and I would like to know if anyone has any experience with COM Object via ASP and the best threading model to use depending on the user load. For instance I know the VB is simple to develope in but we are limited to apartment threading (how much does this really matter if we only have 10000 users or so?) At what point does the threading model really become an issue? Now I know in C++ or J++ Free or Both threading model can be used, (how many users must I surpass to really start having a visuble effect on performance. Any info in this department would be very helpful

Thanks

Stefan

 

[palbano]

Stefan, i don't believe number of users is relevent. in asp ur objects should be stateless so concurrency is not a real issue. Also if you go to .NET then COM is not an issue. Take a look at some of the statements Don Box has made regarding .NET, u can find them easily on the search engines.

-pete

 

[LazyMe]

STA or MTA is not really an issue when writing inet apps (unless you're writing out of process servers); every client that connects to your inet server will get it's own process and therefore get a "fresh" copy of the COM server. I don't know if it's possible to write multithreaded inet app's, but my guess is not, or at the least it won't be done much.

Free threaded means nothing more than that your COM object will be created in a multi threaded apartment. I don't know what kind of apartment will be created by the inet server (STA or MTA), but I think it will be STA. It's important that you try to figure that out; you should create your COM server to be able to load into the same kind of apartment as the client app creates (this prevents the need for marshalling calls to your server). If you want to be absolutely safe, then you could write a server that's able to live in an STA as well as in an MTA (Both, like you mentioned), but I think that STA will do....
Greetings,
Rick