e3098a8e32
This is for topics which do not easily fit into specific topics but are more about overall style or general attitude of approach. For an initial proposal, diversity of clients seems a good guideline. Change-Id: I70d54a0ce98b7a583ba0b1e171b89d206acad98f
17 lines
565 B
ReStructuredText
17 lines
565 B
ReStructuredText
|
|
General
|
|
=======
|
|
|
|
This topic document serves to provide guidance on general topics of
|
|
style and approaches to developing and managing public HTTP APIs.
|
|
|
|
Guidelines
|
|
----------
|
|
|
|
1. While every public API should have a canonical client
|
|
implementation we should discourage tight bindings between an API
|
|
and its clients and strongly encourage separate evolution of
|
|
the API and its official client. We welcome any effort aimed at
|
|
developing and promoting alternative clients. A diversity of
|
|
implementations is healthy and enables use in many environments.
|