Convergence RPC calls

[domob]

I noticed that Convergence's routine for RPC calls (in getNamecoinDnsField or so) is very complicated, using a low-level Mozilla API. While it works, what do you think about switching over to the code used by the NameID extension to perform RPC calls? I think it is less complicated, but of course that's just a matter of taste. Since the code is already there and working, it won't change that much for maintainance. But if you think that is a good idea, I can work on a patch.

[phelix]

Sounds good but it should be biolizard89's decision.

[biolizard89]

I noticed that Convergence's routine for RPC calls (in getNamecoinDnsField or so) is very complicated, using a low-level Mozilla API. While it works, what do you think about switching over to the code used by the NameID extension to perform RPC calls? I think it is less complicated, but of course that's just a matter of taste. Since the code is already there and working, it won't change that much for maintainance. But if you think that is a good idea, I can work on a patch.

nmcontrol uses TCP RPC rather than HTTP RPC like namecoind. I believe NameID uses namecoind, so HTTP, is that correct? I couldn't find a better way of doing TCP RPC via a Firefox extension... is there something I missed?

[domob]

I noticed that Convergence's routine for RPC calls (in getNamecoinDnsField or so) is very complicated, using a low-level Mozilla API. While it works, what do you think about switching over to the code used by the NameID extension to perform RPC calls? I think it is less complicated, but of course that's just a matter of taste. Since the code is already there and working, it won't change that much for maintainance. But if you think that is a good idea, I can work on a patch.

nmcontrol uses TCP RPC rather than HTTP RPC like namecoind. I believe NameID uses namecoind, so HTTP, is that correct? I couldn't find a better way of doing TCP RPC via a Firefox extension... is there something I missed?

Yes, NameID uses namecoind and HTTP. But if IIRC (have to check that), the HTTP-part is done manually, so it would be easy to remove it from the code. I believe the TCP API used is on a higher level than the one used in Convergence. Would you oppose to changing that if my assumptions turn out to be true and I provide a patch?

[biolizard89]

I noticed that Convergence's routine for RPC calls (in getNamecoinDnsField or so) is very complicated, using a low-level Mozilla API. While it works, what do you think about switching over to the code used by the NameID extension to perform RPC calls? I think it is less complicated, but of course that's just a matter of taste. Since the code is already there and working, it won't change that much for maintainance. But if you think that is a good idea, I can work on a patch.

nmcontrol uses TCP RPC rather than HTTP RPC like namecoind. I believe NameID uses namecoind, so HTTP, is that correct? I couldn't find a better way of doing TCP RPC via a Firefox extension... is there something I missed?

Yes, NameID uses namecoind and HTTP. But if IIRC (have to check that), the HTTP-part is done manually, so it would be easy to remove it from the code. I believe the TCP API used is on a higher level than the one used in Convergence. Would you oppose to changing that if my assumptions turn out to be true and I provide a patch?

Most likely I'd be fine with that, but I'd appreciate it if you can send me a link to some info on the TCP API you're using so I can take a look before you write the patch. But yeah, I agree that the API used in FreeSpeechMe is a pain... I'm not sure why Moxie would have used an unnecessarily low-level API... making it more readable would certainly be a plus.