path: root/doc
diff options
authorSchanzenbach, Martin <>2018-04-03 11:07:56 +0200
committerSchanzenbach, Martin <>2018-04-03 11:07:56 +0200
commite331d5f6dfb406f9c56d4b3cb69b671b317d6992 (patch)
treeafeb14e96833708744a8fbc72fdbbba5022564a4 /doc
parent1c8221b08904f8c8b9aefd5e2aeec648bcc7e1e4 (diff)
start REST documentation
Diffstat (limited to 'doc')
1 files changed, 54 insertions, 0 deletions
diff --git a/doc/documentation/chapters/developer.texi b/doc/documentation/chapters/developer.texi
index c7d7ddaac..e95355302 100644
--- a/doc/documentation/chapters/developer.texi
+++ b/doc/documentation/chapters/developer.texi
@@ -75,6 +75,7 @@ new chapters, sections or insightful comments.
* REVOCATION Subsystem::
* File-sharing (FS) Subsystem::
* REGEX Subsystem::
+* REST Subsystem::
@end menu
@node Developer Introduction
@@ -8365,3 +8366,56 @@ <input path> <outfile>
to create a search strings file from the previously created
regular expressions.
+@cindex REST subsystem
+@node REST Subsystem
+@section REST Subsystem
+@c %**end of header
+Using the REST subsystem, you can expose REST-based APIs or services.
+The REST service is designed as a pluggable architecture.
+To create a new REST endpoint, simply add a library in the form
+The REST service will automatically load all REST plugins on startup.
+The rest service can be configured in various ways.
+The reference config file can be found in
+@end example
+The port as well as Cross-origin resource sharing (CORS) headers that
+are supposed to be advertised by the rest service are configurable.
+* Namespace considerations::
+* Endpoint documentation::
+@end menu
+@node Namespace considerations
+@subsection Namespace considerations
+The gnunet-rest-service will load all plugins that are installed.
+As such it is important that the endpoint namespaces do not clash.
+For example, plugin X might expose the endpoint ``/xxx'' while plugin Y exposes
+endpoint ``/xxx/yyy''.
+This is a problem if plugins X is also supposed to handle a call to
+Currently, the REST service will not complain or warn about such clashes so
+please make sure that endpoints are unambiguous.
+@node Endpoint documentation
+@subsection Endpoint documentation
+This is WIP. Endpoints should be documented appropriately.
+Perferably using annotations.