Consider renaming arpa2api --> internetwide-shell
The individual projects have shells named arpa2reservoir
, arpa2acl
and so on. They will come from modules named arpa2.reservoir.shell
and arpa2.acl.shell
and are installed as entry_points
calling their :main
function.
The arpa2shell
spans those shells, and makes it easy to go from one to another.
What arpa2api
and arpa2api.d
add goed well beyond that. It makes the shells universally available, using end-to-end protection to have an authenticated identity for ACL evaluation. This makes heavy use of the ideas of realm crossover and thorough authentication and encryption founded in SASL and Kerberos.
This is why it may be useful for this implementation to step out and advertise itself as part of the InternetWide Architecture, and call itself internetwide-shell
. This parallels a recent though to use the AMQP infrastructure between Reservoir instances as internetwide-reservoir
. (We can still add .d
or -server
to indicate the server as a separate process, which almost always makes sense.)
Note that this would be a naming approach for a few programs in a larger ARPA2 package. The individual shells will continue to be named like arpa2reservoir
; it is local in nature and is basically a software project that does not cross the network.