Felipe Magno de Almeida <felipe.m.almeida <at> gmail.com> writes:
Wouldnt this be possible?
std::string foo(std::string);
rcf::server s(endpoint); rcf::binder<std::string(std::string)> echo(&foo);
int main() { s.register("IEcho", echo); server.run(); // blocks return; }
It certainly is possible, and it's something I want to implement, but as you say it doesn't cover the case where you want to expose an interface consisting of several functions.
Yes, what I wanted to say(but forgot to) is that RCF could use it. As it could use shmem and asio for IPC. That would make rcf with a cleaner interface. BTW, I dont like very much the RCF namespace all in caps, it seems like a macro. But that's just an aesthetic issue.
Yeah, Rcf:: would be better. I've just gotten so used to the caps that I don't see them :) Regards, Jarl