Temp

> So, I'm not really sure what you actually mean by NMControl client libraries.  It's JSON-RPC, every language worth mentioning already has libs for this.  What exactly do you want the libs to accomplish?

Not much, nothing like what I was proposing before. Maybe discovery and parsing of namecoin.conf and a few language specific niceties.  As you said, new abstractions should be done through NMControl.

The impetus for this is my experiences porting an JSON-RPC Bitcoin library and trying to write one from scratch. The Bitcoin library came complete with unit tests, so it should have just worked. However, I had to chase down weird bugs which required implementing dirty hacks within the JSON-RPC library. The issues I ran into with the Haxe library were bad enough that I had to use Wireshark to figure out what was wrong.

Maybe that's a trivial task for real programmers, but it was really hard for me. Providing libraries removes that upfront gruntwork and a improves the overall development experience. Namecoin has a steep enough learning curve as is, why make people figure out the JSON-RPC interface was well?

Once complete, it also doesn't seem like it will require a whole lot of maintenance. One code base, top-notch support in 4-6 languages ... that's a pretty high-impact project.


> sdgathman seems willing to do documentation for NMControl.  Do you have any objections to this?

No, I think we should try to recruit new contributors whenever possible.  Do you think he wold be up for writing a Barrister-RPC IDL spec?