Ruben Verborgh

> From that point of view this issue should be classed as a **bug** not an enhancement. @timbl I'm afraid this would lead us onto a rather slippery slope. I'm...

@TallTed Your comment seems to pertain to a different issue (https://github.com/solid/specification/issues/342). This issue is about `PATCH`, the goal of which is—by definition—to not preserve everything as uploaded.

@argahsuknesib Can we generalize this to "notifications need to work with multiple threads", such that the existing multi-threaded Webhooks are valid solution? (WebSockets are not a well-scalable technique in general,...

Can we keep this one open but assign to @argahsuknesib to 1. report back on usage of multiple threads 2. detail any remaining problems after that?

> So the question is: how can we go beyond +/- 50req/s? Definitely multiple threads (that's always the secret to scalable performance), and Webhooks. Whereas there are opportunities to optimize...

> * Update the main template that links to `util.js` to add a query ~~/hash~~ parameter to the link containing a version number so it gets updated after every release....

We have open issues regarding validation though; I wonder if a first validator we can write is a streaming RDF parser. It's an interesting problem as well, because what do...

At first I thought that SPARQL.js was to blame for parsing the query, but the SPARQL 1.1 grammar explicitly allows it. However, the [SPARQL 1.1 Update spec](https://www.w3.org/TR/sparql11-update/#deleteInsert) states: > [DELETE/INSERT]...

To what extent is a quick win to mount S3 to the filesystem? https://www.nakivo.com/blog/mount-amazon-s3-as-a-drive-how-to-guide/

Additionally, if _all_ requests are rejected (in the case of `PUT`), we should 405 rather than 409.