Henry Story

Btw. On a slightly related topic: the akka.http group should make a pull request to add itself to the [http-wg's list of HTTP/2.0 implementations](https://github.com/httpwg/http2-spec/wiki/Implementations).

Quic is not the end of improvements btw. I found [Why Quic is not the Next Big Thing](https://medium.com/codavel-blog/quic-vs-tcp-tls-and-why-quic-is-not-the-next-big-thing-d4ef59143efd), but it is made from the point of view of a competing...

(If I had the skills) I would consider reducing my work by using a thin wrapper written in another language like Quiche4J above :-) That would allow me to see...

I think AWS-Signature is now the IETF HTTP-Bis spec "Signing Http Messages" which is at version 07. I have an implementation of that here for Akka. https://github.com/bblfish/httpSig

@timbl wrote: > This would of course all be much easier if ACP has been formed as a set of extensions to WAC. There has been a call for ACP...

It does not need a lot to get this through. Just some work on improving the language a little bit.

The nice thing is that for servers where all resources have their own Access Control Resource, as advocated currently by ACP, `acl` and `acp:AccessControl` will coincide. For servers like existing...

So here is the definition from the [ACP draft spec (pushed recently but not reviewed)](https://solid.github.io/authorization-panel/acp-specification/#access-control) for the URL `http://www.w3.org/ns/solid/acp#accessControl` > The ACP accessControl predicate defines the set of access controls...

> I don't understand the motivation for this. WAC and ACP address different use cases. They are both addressing access control use cases. That is all the client at the...

@acoburn wrote > The only way this scales is by introducing a paging mechanism such that you limit the scope of authZ enforcement to a predictable window size, which is...