Hello, Yes Channel already support transparent distributed message passing among different processes (among different machines thru ASIO and in the same machines thru Interprocess shared memory queues), there are tutorial samples for both scenarios. The messages are marshaled/demarshaled using Boost.Serialization. However Channel is for asynchronous message passing, so it is a one-way, no-return call. To implement request-response style RPC, the caller should pack a response -id/name in the request message and wait on the response-id/name; and the callee at the other end can return the result with the response-id/name. Regards, Yigong On 4/16/07, Stjepan Rajko <stipe@asu.edu> wrote:
Well, I threw together a little hack of a marshalling wanna-be framework... Files attached. Implementation is ..eh.., and the ....... Anyway, If Channel can already do this, cool... If not and someone wants to lead getting a marshalling thing together,