3 ms·
I agree with this personally, because this spec is adding meta-data to the body, and headers are pretty much made for that. The practical problem is that you h
by pfraze 14y ago
I agree with this personally, because this spec is adding meta-data to the body, and headers are pretty much made for that.
The practical problem is that you have to parse the link header, and it's not simple enough for common use. I think, if we want to use headers, we need to build some JS utilities for the different specs that abstract away any parsing.
- AffableSpatula 14y agoAlready exists: https://github.com/s3u/headers.js https://github.com/s3u/headers.js There are problems with using Link headers, I think you will find less friction in practice by treating links as 'proper data' and putting them in the content body using a media type like this.
- pfraze 14y agoOh, awesome, thanks. You may be right-- HTML employs meta-data in the header, and there are good reasons for it. I like to think that I can put my meta links in the headers and content links in the json, but I may be overworking for a minor gain in simplicity.