41 lines
1.5 KiB
Plaintext
41 lines
1.5 KiB
Plaintext
From: mkersey at metricom.com (Michael Kersey)
|
|
Date: Tue, 06 Apr 1999 16:35:06 -0500
|
|
Subject: Python under ASP/MTS
|
|
References: <3709C492.EED3BF03@parkey.com>
|
|
Message-ID: <370A7E0A.3C8D79B9@metricom.com>
|
|
Content-Length: 1216
|
|
X-UID: 855
|
|
|
|
If you instantiate the Python COM object at the application level, then it
|
|
should be resident and available immediately. You could instantiate one or
|
|
more of these COM objects at the Application level and keep them in a pool.
|
|
This should eliminate any unloading/reloading problem. Allocate them to
|
|
incoming ASP requests as needed.
|
|
Good Luck,
|
|
Michael D. Kersey
|
|
|
|
Carol Parkey wrote:
|
|
|
|
> We have to build something quickly for a client, but we have to fit
|
|
> within their ASP/MTS mandate.
|
|
> I have developed the first cut of a Python COM object which sits under
|
|
> Microsoft Transaction Server, and can be called from an Active Server
|
|
> Page in VBScript/JavaScript (thanks to Mark Hammond and all the FAQ
|
|
> writers). The requirement is perfect for Python, since it has to
|
|
> convert between user requests in XML and mainframe messages in some
|
|
> hideous format, plus some other fiddly bits.
|
|
> I am concerned, though, about whether I will experience performance
|
|
> problems, with the interpreter being loaded and unloaded. Am I worrying
|
|
> needlessly, or is there something I should be doing (like forcing the COM
|
|
> object's reference count to never drop to zero)?
|
|
> All suggestions gratefully received
|
|
>
|
|
> regards
|
|
>
|
|
> jp
|
|
|
|
|
|
|
|
|
|
|