BrunetRpc over XmlRpc

[David Isaac Wolinsky]

As we discussed in the meeting, TaeWoong can have a remote node perform
a query / cache use XmlRpc over BrunetRpc as opposed to using XmlRpc to
the remote node.

The key is the use of ISenders. When using localproxy, the ISender is
the local node, whereas with proxy, the sender can be an AHSender. So
the ideal case would be to initiate a proxy call via:

rpc.proxy(node_addr, 3, expected_result_count, method, args)

From:
[XmlRpcMethod]
public object[] proxy(string node, int ahOptions, int maxResultsToWait,
string method, params object[] args) {
Address target = AddressParser.Parse(node);
AHSender s = new AHSender(_node, target, (ushort)ahOptions);
return this.Proxy(s, maxResultsToWait, method, args);
}

Regards,
David

[David Isaac Wolinsky]

Also, I would suggest that code such as DeeToo client interface, once in
production, should only be callable from the local node and not remote
nodes. If it were left open, it could be a security hole.

David

> --
>
> You received this message because you are subscribed to the Google Groups "acis.p2p" group.
> To post to this group, send email to aci...@googlegroups.com.
> To unsubscribe from this group, send email to acisp2p+u...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/acisp2p?hl=en.
>
>
>
>

[P. Oscar Boykin]

I think uriproxy should be used and the old interface deprecated.  That was the reason for all the ToUri and SenderFactory work in the first place.