Subject: Re: [boost] [RPC] Compile-time reflection for RPC and mocking
From: Brian Wood (woodbrian77_at_[hidden])
Date: 2014-12-09 15:02:23
Peter Bindels writes:
> Based on Hartmut's speech last Saturday introducing HPX and explaining a
> bit about async/future/promise I tried to implement a simple RPC
> that uses then to decouple work and the result I have so far is very
> promising. I have a simple interface with a call that returns a future,
> the caller does not distinguish between calling the actual object and
> calling on a proxy, as both return a future<T>. It does what the
> mentions - serialize the name of the interface and function, as well as
> arguments (basically the mangled name of the interface function) to
> there are no mismatches.
I tend to agree with Bjorn's post about messaging middleware.
For some reason, thinking in terms of messages is easier for
me. For example, rather than serializing the name of the interface
and function, I include a message id, which is often one byte.
-- Brian Ebenezer Enterprises - So far G-d has helped us. http://webEbenezer.net
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk