diff options
author | Lars Wirzenius <liw@liw.fi> | 2018-10-30 14:50:36 +0200 |
---|---|---|
committer | Lars Wirzenius <liw@liw.fi> | 2018-10-30 14:50:36 +0200 |
commit | 6e5b3c500267bdb6c18528da0e9235e1feb3a99c (patch) | |
tree | 6aa8f1fa9214b8142005bd50062e3e0ae768ba75 | |
parent | 8969020ef7a6eeba9b082ee7db5a82b05a513d83 (diff) | |
download | muck-poc-6e5b3c500267bdb6c18528da0e9235e1feb3a99c.tar.gz |
Fix: typos
-rw-r--r-- | README | 10 |
1 files changed, 5 insertions, 5 deletions
@@ -20,14 +20,14 @@ expected signing key is a key Muck configuration item. I use Qvisqve for my OpenID provider, but any provider should work. Access control is currently very simplitic, but will be improved -later. The goal is to have allow access to be specified per user, per -resource and per operation. +later. The goal is to allow access to be specified per user, per +resource, and per operation. Muck is currently a single-threaded Python program using the Bottle.py framework and its built-in HTTP server. The production version of Muck will probably be written in Rust for performance. The current Python -version can do order of 900 requests per second on a Thinkpad X220 -laptop (plain HTTP over localhost). The goal is to have the Rust +version can do in the order of 900 requests per second on a Thinkpad +X220 laptop (plain HTTP over localhost). The goal is to have the Rust version be able to do at least 50 thousand requests per second. Comments? Feedback? Bug reports? Patches? @@ -110,7 +110,7 @@ The API has two endpoints: `/res` for resources, `/search` for search. Resources are managed as follows: * `POST /res` — create a new resource (need `create` in scope) -* `PUT /res` — update an existingresource (need `update` in scope) +* `PUT /res` — update an existing resource (need `update` in scope) * `GET /res` — retrieve a specific resource (need `show` in scope) * `DELETE /res` — delete a specific resource (need `delete` in scope) |