API Theory about eos HOT 4 CLOSED

I believe this is accurate, except that there is no need to expose it as an fc::api object, in fact it should just be a simple class that anyone can call given a pointer.

The fc::api can then use that simple class to define a generic interface that is implementation independent.

from eos.

Also, all API calls take a single argument, a struct containing the parameters, and return a single value, a struct containing the results.

from eos.

All APIs need to be documented throughly via doxygen in a manner that is easily accessible:

https://eosio.github.io/eos/group__eosiorpc.html

from eos.

This issue has been complete for a long time. Although documentation could always be improved.

from eos.