User-agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
On 10/20/2014 12:28 PM, Hallvard Trætteberg wrote:
Yes, this was what I was thinking of. The advantage is that the
framework does a bit more for you, and you 'reuse' the async interface
that you already defined for the caller.
Right. It may very well make sense to create a new/customized
distribution provider to do this for you, and ECF's provider
architecture makes this very natural (e.g. you could even very simply
extend an existing provider).
If you decide it would be worth it to do this we can certainly continue
technical/implementation discussion in those directions (new/extended
distribution provider). Just let me/all know.