On 17/04/2008, jimmyfrank <[EMAIL PROTECTED]> wrote:
>
> 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
> stateles
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
con
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
con
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
> connectio