Commit 63179d76 authored by Jeremy Soller's avatar Jeremy Soller

Merge branch 'master' into 'master'

Grammar cleanup

See merge request redox-os/book!137
parents edde46ed 09d09bda
......@@ -25,7 +25,7 @@ Opening a URL
Opening URLs happens through the `OPEN` system call. `OPEN` takes a C-like, null-terminated string, and two pointer-sized integers, keeping the open flags and the file mode, respectively.
The path argument of `OPEN` does not have to be an URL. For compatibility reasons, it will default to the `file:` scheme. If otherwise specified, the scheme will be resolved by the registrar (see [The root scheme]), and then opened.
The path argument of `OPEN` does not have to be a URL. For compatibility reasons, it will default to the `file:` scheme. If otherwise specified, the scheme will be resolved by the registrar (see [The root scheme]), and then opened.
> TODO
......
......@@ -12,7 +12,7 @@ In short, a URL is an identifier of a resource. It contains two parts:
2. The reference part. This represents the "payload" of the URL, namely what the URL refers to. Consider `file`, as an example. A URL starting with `file:` simply has a reference which is a path to a file. The reference can be any arbitrary byte string. The parsing, interpretation, and storage of the reference is left to the scheme. For this reason, it is not required to be a tree-like structure.
So, the string representation of an URL looks like:
So, the string representation of a URL looks like:
```
[scheme]:[reference]
......
"Everything is an URL"
"Everything is a URL"
======================
"Everything is an URL" is an important principle in the design of Redox. Roughly speaking it means that the API, design, and ecosystem is centered around URLs, schemes, and resources as the main communication primitive. Applications communicate with each other, the system, daemons, etc, using URLs. As such, programs do not have to create their own constructs for communication.
"Everything is a URL" is an important principle in the design of Redox. Roughly speaking it means that the API, design, and ecosystem is centered around URLs, schemes, and resources as the main communication primitive. Applications communicate with each other, the system, daemons, etc, using URLs. As such, programs do not have to create their own constructs for communication.
By unifying the API in this way, you are able to have a consistent, clean, and flexible interface.
......
......@@ -10,7 +10,7 @@ What does "Everything is a URL" mean?
These can be used for effectively modulating the system in a "non-patchworky" manner.
The term is rather misleading, since a URL is just the identifier of a scheme and a resource descriptor. So in that sense "Everything is a scheme, identified by an URL" is more accurate, but not very catchy.
The term is rather misleading, since a URL is just the identifier of a scheme and a resource descriptor. So in that sense "Everything is a scheme, identified by a URL" is more accurate, but not very catchy.
So, how does it differ from files?
----------------------------------
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment