Open GoogleCodeExporter opened 8 years ago
Thanks for reporting this. It's not possible in RCF 1.2 to specify a specific
client side network interface, but I've added it to the list of features for
RCF 1.3.
Original comment by jarl.lin...@gmail.com
on 15 Nov 2010 at 1:33
OK, thanks for the answer.
I could work around this issue if I could know, on the server, the IP of the
RcfServer handling the remote object. Now, I get this information using the
function RCF::getCurrentRcfSession().getRemoteAddress().string() to get the
client's IP address using the object. Is there any similar function to get the
RcfServer IP address serving the object?
For instance I have an object, and I export it through two RcfServers:
/* Servers */
RCF::RcfServer server_1(RCF::TcpEndpoint(ip_1, port));
RCF::RcfServer server_2(RCF::TcpEndpoint(ip_2, port));
/* Exported object */
MyClass objRef;
server_1.bind<I_MyClass>(objRef);
server_2.bind<I_MyClass>(objRef);
Could the own object objRef know which RcfServer is using it? For example,
getting through some function the IP associated to that server instance.
Once again, thank you.
Original comment by rafael.a...@gmail.com
on 16 Nov 2010 at 7:51
From within your server implementation functions, you can call:
RCF::getCurrentRcfSession().getRcfServer()
, and that will give you the RcfServer the call came in on... Hope that helps.
Original comment by jarl.lin...@gmail.com
on 17 Nov 2010 at 1:04
Hello again. I've tried RCF 1.3 including "setLocalIp" in order to bind the
client to a specific local interface. It seems to work so I think this issue
could be closed.
Thank you for your time and work.
Original comment by rafael.a...@gmail.com
on 17 Jun 2011 at 12:27
Original issue reported on code.google.com by
rafael.a...@gmail.com
on 12 Nov 2010 at 12:55