Skip to content
Snippets Groups Projects
Commit 73689f64 authored by Sébastien Blin's avatar Sébastien Blin
Browse files

Update Name Server Protocol

parent 3fb6addf
Branches
Tags
No related merge requests found
Show whitespace changes
Inline Side-by-side
technical/Name-Server-Protocol.md
+ 3
− 3
View file @ 73689f64
The protocol used by Ring to query and register a name is based on an The protocol used by Jami to query and register a name is based on an
HTTP HTTP
[REST](https://en.wikipedia.org/wiki/Representational_state_transfer) [REST](https://en.wikipedia.org/wiki/Representational_state_transfer)
API answering requests with JSON documents and regular HTTP status API answering requests with JSON documents and regular HTTP status
codes. codes.
The public nameserver is hosted at `ns.ring.cx` and uses a blockchain as The public nameserver is hosted at `ns.jami.net` and uses a blockchain as
its backend. Another implementation could use any other database or its backend. Another implementation could use any other database or
directory service making the nameserver protocol reusable. directory service making the nameserver protocol reusable.
...@@ -74,7 +74,7 @@ username is returned if one is registered on the name server. ...@@ -74,7 +74,7 @@ username is returned if one is registered on the name server.
### Request ### Request
A request for the RingID `ring:29347542eb07159f316577e1ae16243d152f6b7b` A request for the ID `ring:29347542eb07159f316577e1ae16243d152f6b7b`
is a `GET` request with is a `GET` request with
`/addr/`*`29347542eb07159f316577e1ae16243d152f6b7b`* as the URI. `/addr/`*`29347542eb07159f316577e1ae16243d152f6b7b`* as the URI.
......
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment