[rabbitmq-discuss] dotnet client background thread

Brian Lalor blalor at bravo5.org
Fri Dec 16 14:53:04 GMT 2011

On Dec 16, 2011, at 9:43 AM, Tony Garnock-Jones wrote:

> Stepping back from the immediate problem, the "real" solution is to have the JVM and .NET virtual machines grow up and behave like proper systems, complete with lifecycle events. Then, AMQP connections have a chance to clean up and disconnect on their own, without special action on the part of the programmer and without unduly delaying or preventing VM shutdown.

If you use Spring, you get events like these.  With Spring for Java, you can use the destroy-method attribute of the  <bean />  element to invoke a method when the context is shutting down.  I haven't used Spring with .Net, but I'd be surprised if there weren't a similar mechanism there.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20111216/bf50696b/attachment.htm>

More information about the rabbitmq-discuss mailing list