|
From: RefuX Z. <re...@ya...> - 2002-04-29 17:42:32
|
I was just thinking it could be a helpful housekeeping
feature. Kinda like how we close resultsets,
connections etc..
--- David Colwell <dco...@sp...> wrote:
> You hit it - the idea was that the queue facade
> could be long lived, but
> many senders may come and go. In the spirit of
> releasing resources as soon
> as possible, the interface was made as such.
>
> Dave
>
> -----Original Message-----
> From: RefuX Zanzebarr
> To: arc...@li...
> Sent: 4/26/02 4:35 PM
> Subject: [Arch4j-developers] ARCH4J JMS
>
> I looking at the ARCH4J MessageQueueFacade JavaDoc's
> example code:
>
> --- snip ---
>
> MessageQueueFacade qFacade =
>
MessagingProvider.getProvider().getMessageQueueFacade(false);
>
>
> QueueSender sender =
> qFacade.createQueueSender("exampleQueue");
>
> qFacade.startConnection();
>
> TextMessage message = qFacade.createTextMessage(new
> StringBuffer("Hello Whirled"));
>
> sender.send(message);
>
> sender.close();
>
> qFacade.close();
>
> --- snip ---
>
> and was thinking, why don't we just do the
> 'sender.close()' in qFacade.close() ?
> I understand there could be multiple QueueSenders
> within the scope of one QueueFacade instance, but
> there's no reason why we couldn't track them all and
> just close them all (if they're not already closed)
> automagically on qFacade.close()
>
> Thoughts?
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Games - play chess, backgammon, pool and more
> http://games.yahoo.com/
>
> _______________________________________________
> Arch4j-developers mailing list
> Arc...@li...
>
https://lists.sourceforge.net/lists/listinfo/arch4j-developers
>
__________________________________________________
Do You Yahoo!?
Yahoo! Health - your guide to health and wellness
http://health.yahoo.com
|