Comments (5)
Mostly to keep things short. We did the same with extensible HTTP priorities using u
for urgency and i
for incremental.
I think we're fine either way but the HTTP working group usually seems to skew towards brevity.
from compression-dictionary-transport.
We didn't do this for https://w3c.github.io/reporting/#header. Seems unfortunate we're not consistent here.
If this is going for TAG review, could you ask about this? It seems https://w3ctag.github.io/design-principles/#naming-is-hard is in need of an update.
from compression-dictionary-transport.
Looks like the reporting header is a flat dictionary with no pre-defined keys (each key is a "name" for the given endpoint).
We're still pre-experiment so it's a good time to make changes. I'll default to long prefixes as the starting point and see if shortening is necessary. We're already using base-16 hash strings instead of base-64 for convenience over brevity.
from compression-dictionary-transport.
Brevity, yes, but that's usually regarding ReallyPointlesslyLongHeaderNames
. I don't think you'd get much pushback on path
vs p
(although I agree someone will say something).
from compression-dictionary-transport.
While we're looking at the naming, would match
be clearer than path
to the extent that what is being specified is the path-matching rule to be used for future requests?
from compression-dictionary-transport.
Related Issues (20)
- No support for hash-based versioning HOT 2
- sec-fetch-dest for dictionary fetch HOT 8
- Allow for hash/versions in the middle of the path HOT 2
- Add cross-origin compression protection
- Copy edit issue HOT 1
- Consider making sec-available-dictionary: value path-safe
- Standards positions HOT 3
- i.e. vs e.g.
- Path parsing HOT 3
- Grabbing authority for paths closer to the root HOT 3
- Consider Websocket use case HOT 9
- Consider support other Content-Encoding schemes HOT 2
- Clear Site Data for dictionaries HOT 10
- Exposing storage usage for dictionaries HOT 10
- Dictionary partitioning in browsers without tripled-keyed HTTP cache HOT 1
- Define mechanism for advertising non-bytestream dictionary formats
- Content-encoding may be fragile
- Consider options for Path of side-loaded dictionaries HOT 1
- Hashes, algorithm agility, and overlap with HTTP digests. HOT 7
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from compression-dictionary-transport.