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

linkset payload in HTTP header #121

Open
hvdsomp opened this issue Aug 1, 2019 · 3 comments

Comments

@hvdsomp
Copy link
Collaborator

commented Aug 1, 2019

I am not so sure anymore why we decided it was a good idea to allow providing a linkset payload as the content of the Link header of the link set resource:

  • It can only be done for linksets formatted according to the application/linkset format, not for the application/linkset+json format.
  • It seems to go against a major motivation for introducing link sets, i.e. HTTP headers can become too large when many links need to be provided.
  • It requires clients to go look in two places to find linkset payloads: in the header and the body of the linkset resource.

Would it not be more elegant to provide linkset payloads only as the body of the link set resource?

@hvdsomp hvdsomp added the linkset label Aug 1, 2019

@dret

This comment has been minimized.

Copy link
Owner

commented Aug 1, 2019

@hvdsomp

This comment has been minimized.

Copy link
Collaborator Author

commented Aug 1, 2019

@dret

This comment has been minimized.

Copy link
Owner

commented Aug 1, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.