> Does anyone know how to create a MTS pool of PerlCOM objects? Or is
> there
> another solution beside the pooling, to increase performance? I know
> some people create an instance of PerlCOM inside an Application
> variable, but this means serialization of the object's access, and the
> issue here is exactly scalability.
You could create a "pool" in the Application instead of storing only one
PerlCOM object.
Then you only have to serialize the acquiring/returning the object from/to
the pool.
The problem is ... it seems to me that you can't store even single PerlCOM
object in Aplication. I get
==================
Application object error 'ASP 0197 : 80004005'
Disallowed object use
/testPool/Index.asp, line 28
Cannot add object with apartment model behavior to the application intrinsic
object.
==================
if I try that.
Thought ... <OBJECT> works so you may create several instances this
way, store in the session which ones are being used and if someone wants
an instance give him one from the pool (or a new not pooled one).
How to return them to the pool reliably ... GOK.
Jenda
== [EMAIL PROTECTED] == http://Jenda.Krynicky.cz ==
: What do people think?
What, do people think? :-)
-- Larry Wall in <[EMAIL PROTECTED]>
_______________________________________________
Perl-Win32-Web mailing list
[EMAIL PROTECTED]
http://listserv.ActiveState.com/mailman/listinfo/perl-win32-web
