Changes between Version 7 and Version 8 of i2pcontrol


Ignore:
Timestamp:
Jan 25, 2016 4:18:33 PM (5 years ago)
Author:
tuna
Comment:

—

Legend:

Unmodified
Added
Removed
Modified

  • i2pcontrol

    v7 v8  
    3434== Prefixes ==
    3535
    36 The naming for will be done similar to how it's done in CSS, with vendor prefixes for the different API implementations (i2p, kovri, i2pd).
     36The RPC naming scheme similar to how it's done in CSS, with vendor prefixes for the different API implementations (i2p, kovri, i2pd).
    3737
    3838{{{
    … …  
    4343}}}
    4444
    45 The overall idea with vendor specific prefixes to allow for some wiggle room and let vendors innovate without having to wait for every other implementation to catch up.
    46 If is implemented by all implementations it can be moved under the umbrella of the next API version
     45The overall idea with vendor specific prefixes to allow for some wiggle room and let implementations innovate without having to wait for every other implementation to catch up.
     46If a RPC is implemented by all implementations it's multiple prefixes can be removed and it can be included as a core RPC in the next API version.
    4747
    4848