OWC10 server side use in multi-user environment

[Vitalik]

Hello there,

Since OWC controls' main purpose is to be used on the client and they are
COM components, do they support MTA or STA threading models? We plan on
using the spreadsheet component from ASP.NET and our concern is that
spreadsheet component may not be suitable for heavy multi-user server
applications (supporting calculations using different spreadsheets for many
users). If that's the case, is anything can be done?

TIA,

Vitaliy

 

[Alvin Bruney]

You are basically correct. Client side components are designed to run within
the hosting process of IE which is an STA model. The important thing here is
not so much the number of users but the number of concurrent users. They are
related but definitely not the same. OWC starts to choke on high number of
concurrent users with threading issues, deadlocks, poor performance and
memory issues. You can get away with a high number of users if the number of
concurrent requests are kept to a minimum. How? No idea. But that's the crux
of the matter.

 

[Alvin Bruney]

COM interop assemblies (PIA) allow managed applications to bind to unmanaged
types at compile time and provide information to the common language runtime
about how the unmanaged types should be marshaled at run time. It doesn't
change the underlying object or apartment model. The issues will still be
there.

 

[Vitalik]

Thanks again, Alvin.

COM interop assemblies (PIA) allow managed applications to bind to unmanaged
types at compile time and provide information to the common language runtime
about how the unmanaged types should be marshaled at run time. It doesn't
change the underlying object or apartment model. The issues will still be
there.

number plan