[Message Prev][Message
Next][Thread Prev][Thread Next][Message
Index][Thread Index]
Re: xPLLib v3.0 Public Beta
- Subject: Re: xPLLib v3.0 Public Beta
- From: Tom Van den Panhuyzen <tomvdp@xxxxxxxxx>
- Date: Sat, 4 Dec 2004 21:48:37 +0100
- References:
<ABE834A33EDA2A7A31.home-automation@jbnet.cns-uk.org>
<6378962485491544547@unknownmsgid>
<26b8eee1041130020056e0c13e@mail.gmail.com>
<WorldClient-F200411301329.AA29490005@jbnet.cns-uk.org>
<26b8eee10411300631750d9d34@mail.gmail.com>
<002401c4d6eb$caef3730$040612ac@corp.frontier.co.uk>
<26b8eee104113007061777823a@mail.gmail.com>
<002f01c4d6f1$5cfe7960$040612ac@corp.frontier.co.uk>
<26b8eee104113007433db95e48@mail.gmail.com>
On Tue, 30 Nov 2004 16:43:44 +0100, Tom Van den Panhuyzen
<tomvdp@xxxxxxx> wrote:
> If the code crashes because of a programming error (say some strange
> packet that makes it crash) it will release the mutex.
> I think the only exception is when you actually kill it via task
> manager. But I should check that. Because mutexes are managed by
> Windows and not the .net framework or some other higher layer it is
> pretty reliable.
To complete the story:
Even killing the app with the task manager releases the mutex.
I had to make a slight modification to the code of xpl lib v3 because
in case the code running the hub exits unexpectedly the mutex is freed
before the socket.
It proves even in disaster scenarios the hub will spring back to life :-)
Regards,
Tom
xPL Main Index |
xPL Thread Index |
xPL Home |
Archives Home
|