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

In fact this is the whiteboard pattern for network services. I have refactored one of my pi services to this pattern and it works like a charm.

#setTemperature(String host, double temperature);



On Tue, Oct 21, 2014 at 6:12 PM, Scott Lewis <slewis@xxxxxxxxxxxxx> wrote:
On 10/21/2014 5:41 AM, Wim Jongman wrote:
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.

Yes, I think you are right that a two services approach could/does work.

The complexities in this case have to do with associating these two services, which are hosted by different processes and so could have very different dynamics.

But again, you are quite right that this is a viable approach.


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