COM Interop -- Class Library vs. EXE
- From: "Gregory Hassett" <ghassett@xxxxxxxxxxx>
- Date: Tue, 27 Dec 2005 09:44:18 -0500
Hello,
I am developing classes in C# that are called from PHP via COM. The C# code
does a lot of work to establish internal data structures, and I would like
these data structures to persist so that I do not have to recreate them each
time the COM code is called.
For example, imagine a function MyObject.BuildInternalDataStructures() which
takes a long time. Another function, MyObject.UseInternalDataStructures(),
is called repeatedly. The first time UseInternalDataStructures is called,
it detects that the structures haven't been built, so it calls
BuildInternalDataStructures. Subsequent calls to UseInternalDataStructures
do not need to incur the penaly of building the internal data structures.
The problem is that on my web server, PHP instantiates a new instance of my
object each time a PHP page is hit -- and destroys the object (and unloads
my DLL) when the page completes executing. So the next time the user hits a
PHP page that calls out to MyObject.UseInternalDataStructures(), it has to
rebuild everything again from scratch.
Is there a way to build a COM server as an EXE, so that it can run in the
background, maintaining its state, while allowing COM consumers (such as
PHP) to call into it?
Thanks
Greg
.
- Follow-Ups:
- Re: COM Interop -- Class Library vs. EXE
- From: Nicholas Paldino [.NET/C# MVP]
- Re: COM Interop -- Class Library vs. EXE
- From: Ignacio Machin \( .NET/ C# MVP \)
- Re: COM Interop -- Class Library vs. EXE
- Prev by Date: Re: iterating through a collection containing different types of numeric values and adding a specified number to the values.
- Next by Date: Re: OO DB question
- Previous by thread: Remote File I/O
- Next by thread: Re: COM Interop -- Class Library vs. EXE
- Index(es):
Relevant Pages
|