[reSIProcate] Scheduling tasks with ExternalMessageHandler

[Scott Godin]

Good question.  I haven't really looked that closely at the
ExternalMessage stuff in detail.  On a quick look it seems that you can
install a chain of handlers if you use the ExternalHandler interface,
and each handler in the chain can decide if the message is handled or
not.  This is a different programming model than the DumCommand
approach, where you put the handling in the actual override message
instead.  You should use whichever approach fits your application
better.  

I agree with your original comment about inheriting ExternalMessage from
ApplicationMessage - this would allow you to use stack::postMS.  Note:
You can dum->post an ExternalMessage, if you're not interested having
the message posted at some time in the future.

Scott

-----Original Message-----
From: resiprocate-devel-bounces at resiprocate.org
[mailto:resiprocate-devel-bounces at resiprocate.org] On Behalf Of Max
Bowsher
Sent: Wednesday, September 24, 2008 9:07 AM
To: resiprocate-devel at resiprocate.org
Subject: Re: [reSIProcate] Scheduling tasks with ExternalMessageHandler

Scott Godin wrote:
> Have a look at using DumCommands instead - more info here:
> http://www.resiprocate.org/DUM_Threading

Aha - is the ExternalMessageBase / ExternalMessageHandler infrastructure
considered deprecated in favour of DumCommands, then?

-- 
Max Bowsher <maxb at mxtelecom.com>
http://www.mxtelecom.com
_______________________________________________
resiprocate-devel mailing list
resiprocate-devel at resiprocate.org
https://list.resiprocate.org/mailman/listinfo/resiprocate-devel