Hi Ashley,<br><br>Indeed, the purpose for having the IModel hanging off the IConnection is to allow a single connection to be shared. Sharing the connection reduces the number of active connections to your server. It also eliminates a potential cause of problems when connections are created and torn down in rapid succession.<br>
<br>If you consider the amount of time taken to establish a connection, then sharing the connection will certainly help increase your message sending performance.<br><br>Paul.<br><br><div class="gmail_quote">On Thu, Sep 10, 2009 at 10:43 AM, Ashley van Gerven <span dir="ltr"><<a href="mailto:ashley.ohq@gmail.com">ashley.ohq@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi,<br><br>The .NET user guide states that IModel instances should not be shared accross threads. So having multiple web requests publishing to the queue using the same IModel instance is not an option. However would it be (a) possible and (b) advantageous to share a IConnection instance, and have each web request create an IModel using the same connection instance? My thought is that sharing the IConnection would speed up message publishing (using BasicPublish).<br>
<br><br>Thanks<br><font color="#888888">Ashley <br>
</font><br>_______________________________________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
<a href="http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
<br></blockquote></div><br>