The application would be either a webservice or an .aspx page a user would hit. So a user might enter some info on a page with a form and then I'd need to create all the activemq resources and send the message. Since it's stateless I'd need to be able to have the connections pooled like MSMQ connections would be pooled. Would Sprint.NET be able to do something similar?
James.Strachan wrote: > > On 17/04/2008, jimmyfrank <[EMAIL PROTECTED]> wrote: >> >> I'm using the .NET Messaging API to send and receive messages from >> ActiveMQ. >> How would I pool connections? Do I need to at all or is it handled >> somehow >> for me by the broker? I can find several forum posts that talk about >> connection pooling when using java JMS but I can't seem to find anything >> that talks about how to do this when using the .NET API's. Do I need to >> use >> the Spring.NET? > > It depends a little on your application. If its a client UI then just > have a single connection and a few sessions and you'll be fine. If its > more of a server, processing messages efficiently in a highly > concurrent manner, then some kinda pooling mechanism such as in > Spring.NET is preferable. > > I've added this to the NMS FAQ... > http://activemq.apache.org/nms/faq.html > -- > James > ------- > http://macstrac.blogspot.com/ > > Open Source Integration > http://open.iona.com > > -- View this message in context: http://www.nabble.com/Connection-pooling-when-use-the-.NET-Messaging-API-%28NMS%29-tp16737663s2354p16744244.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
