1N/AWe use REST over HTTP as the primary networking API between client and
1N/Aserver. That choice means that
1N/A- the client can be reimplemented,
1N/A- the server can be reimplemented, and
1N/A- decorations on a transaction, like authentication, encryption, and
1N/A redirection, can be handled using the enormous technology set around
1N/AThe first two are true of any well-defined protocol, but we benefit in
1N/Athis case from the wide availability of HTTP client and server
1N/Aimplementation starting points.
1N/A Returning a transaction ID
1N/A Plus metadata in submitted headers and contents as file body.
1N/A Dependency metadata in submitted headers.
1N/A Returning package URL.