Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reduce profile list network traffic burden by making optional unless explicitly asked for #11

Open
rob-metalinkage opened this issue Nov 4, 2019 · 2 comments
Assignees
Labels
requires discussion Issue to be discussed in a telecon (group or plenary)

Comments

@rob-metalinkage
Copy link
Contributor

The "cartesian product" form of profile listing can become quite onerous.

We should consider making it a "MAY" to return this for GET requests - and to ensure the mechanism is actually supported making it mandatory only if a specific named profile is asked for - so we'd need to mint that id.

(we could make it HEAD specific - but that violates HEAD=GET without body expectation..)

@larsgsvensson
Copy link
Contributor

I don't think it's a good idea not to list the cartesian product. If we make it mandatory only when the client asks for a specific profile, then there is no way the client can figure out which profiles are available unless it asks for a dummy profile.

@plehegar plehegar transferred this issue from w3c/dxwg Feb 25, 2020
@rob-metalinkage rob-metalinkage added the requires discussion Issue to be discussed in a telecon (group or plenary) label Feb 7, 2024
@rob-metalinkage
Copy link
Contributor Author

Consider along with 300 response #5

Relax spec to say MAY provide complete list but MUST provide link to Altr profile.

This solve server side load to calculate all options.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
requires discussion Issue to be discussed in a telecon (group or plenary)
Projects
None yet
Development

No branches or pull requests

4 participants