/status is separate from all the other node's RPC methods in that it has to work over HTTP(S), while the rest are internal to the network and can potentially use something else (e.g. Noise). Do you think it would be useful to have a separate HTTP port field, in addition to the main one, so that nodes could seamlessly transition to a different protocol in the future?
The transitioning from the previous ABI version can be automatic - just take the HTTP port equal to the main port. Will need a minor change in the Python codebase, to use the HTTP port when rendering the status page.
(In the same vein certificate_der can be renamed to transport_public_key or something, but that's just a cosmetic change)
/statusis separate from all the other node's RPC methods in that it has to work over HTTP(S), while the rest are internal to the network and can potentially use something else (e.g. Noise). Do you think it would be useful to have a separate HTTP port field, in addition to the main one, so that nodes could seamlessly transition to a different protocol in the future?The transitioning from the previous ABI version can be automatic - just take the HTTP port equal to the main port. Will need a minor change in the Python codebase, to use the HTTP port when rendering the status page.
(In the same vein
certificate_dercan be renamed totransport_public_keyor something, but that's just a cosmetic change)