Changes between Version 7 and Version 8 of i2pcontrol
- Timestamp:
- Jan 25, 2016 4:18:33 PM (5 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
i2pcontrol
v7 v8 34 34 == Prefixes == 35 35 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).36 The RPC naming scheme similar to how it's done in CSS, with vendor prefixes for the different API implementations (i2p, kovri, i2pd). 37 37 38 38 {{{ … … 43 43 }}} 44 44 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 version45 The 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. 46 If 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. 47 47 48 48