Hi,
thanks, I 'll post the problem in python-win32@python.org ...
Frank
--
http://mail.python.org/mailman/listinfo/python-list
CTED]
> Sent: Monday, February 14, 2005 12:53 PM
> To: python-list@python.org
> Subject: keeping a COM server alive
>
>
> I have implemented a local COM Server with win32com framework
> where all
> clients
> use the same global object (test_obj). So far it works, but when
Hi !
Sorry, but I receive the mailing list, I had readed THE book (Prog...Win32),
I questioned M.Hammond, I traversed the archives...
But I have no solution.
And, also, a COM server which answers several clients is very smart to
design; in particular because of the temporal re-entry (re-entrance
Do Re Mi chel La Si Do wrote:
Hi !
I had also make a Python-COM-server.
But, when I launch several clients, I obtain several instances of my
COM-server.
Finally, there are advantages and disadvantages in this established fact.
But I can't use this way for to exchange data between several clients. F
Hi !
I had also make a Python-COM-server.
But, when I launch several clients, I obtain several instances of my
COM-server.
Finally, there are advantages and disadvantages in this established fact.
But I can't use this way for to exchange data between several clients. For
that, I use a TCP local s
I have implemented a local COM Server with win32com framework where all
clients
use the same global object (test_obj). So far it works, but when the
last client
is closed the gobal object is deleted because the pythonw.exe is
closed. When I
create a new client a new pythonw process is started. I ne
