[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ecf-dev] Remote service question

Alternatively, you could setup two services, one on each end.

The server sets up RequestService#Request(Request request)
The client sets up CallBackService#DeliverResults(Request originalRequest, Whatever result)

When the server has finished processing the request it calls back the client with the original request and the result.

On top of that, both calls can be done async.



On Mon, Oct 20, 2014 at 10:04 PM, Scott Lewis <slewis@xxxxxxxxxxxxx> wrote:
On 10/20/2014 12:28 PM, Hallvard TrÃtteberg wrote:
<stuff deleted>

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.


ecf-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit