| ... | @@ -8,7 +8,6 @@ The short version is: today "distributed" means non-interoperable, slow and lack |
... | @@ -8,7 +8,6 @@ The short version is: today "distributed" means non-interoperable, slow and lack |
|
|
|
|
|
|
|
This does **not** mean that Fenrir can not be used to build distributed systems. The flexibility of this protocol allows you to build non-federated, distributed protocols.
|
|
This does **not** mean that Fenrir can not be used to build distributed systems. The flexibility of this protocol allows you to build non-federated, distributed protocols.
|
|
|
|
|
|
|
|
Again, much more is explained in the [Federated_vs_Distributed](Federated_vs_Distributed) page.
|
|
|
|
|
|
|
|
|
|
# Details
|
|
# Details
|
|
|
|
|
|
| ... | @@ -133,3 +132,4 @@ The problem of lattice versions is taken care of with the "lattice version" byte |
... | @@ -133,3 +132,4 @@ The problem of lattice versions is taken care of with the "lattice version" byte |
|
|
|
|
|
|
|
The lattice distribution is done the first time a client connects to a service. Since it is the first time, we can authenticate and assume that the user has full access ("top"), but as soon as we have authenticated we transfer the lattice to the client.
|
|
The lattice distribution is done the first time a client connects to a service. Since it is the first time, we can authenticate and assume that the user has full access ("top"), but as soon as we have authenticated we transfer the lattice to the client.
|
|
|
|
|
|
|
|
|
---- |
|
|
|
\ No newline at end of file |
