Comments on: Markus Karg on the Hypermedia Constraint http://www.nordsc.com/blog/?p=376 Mon, 05 Jul 2010 15:38:14 +0000 http://wordpress.org/?v=2.9 hourly 1 By: Mike K http://www.nordsc.com/blog/?p=376#comment-119 Mike K Wed, 17 Feb 2010 01:21:19 +0000 http://www.nordsc.com/blog/?p=376#comment-119 In terms of HTTP, headers can be used for hypermedia purposes, since they're a part of the representation - that's what Link headers are for In terms of HTTP, headers can be used for hypermedia purposes, since they’re a part of the representation – that’s what Link headers are for

]]> By: This Week in REST – Volume 3 (Feb 8 2010 – Feb 14 2010) « This week in REST http://www.nordsc.com/blog/?p=376#comment-102 This Week in REST – Volume 3 (Feb 8 2010 – Feb 14 2010) « This week in REST Mon, 15 Feb 2010 09:25:55 +0000 http://www.nordsc.com/blog/?p=376#comment-102 [...] and HATEOAS mean and the importance of embracing all four REST constraints. (by Markus Jarg) Markus Karg on the Hypermedia Constraint – A response to the previous article concerning the placement of hypermedia data. (By Jan [...] [...] and HATEOAS mean and the importance of embracing all four REST constraints. (by Markus Jarg) Markus Karg on the Hypermedia Constraint – A response to the previous article concerning the placement of hypermedia data. (By Jan [...]

]]> By: Jan Algermissen http://www.nordsc.com/blog/?p=376#comment-96 Jan Algermissen Sun, 14 Feb 2010 19:06:28 +0000 http://www.nordsc.com/blog/?p=376#comment-96 Markus, see your point and its a good one. Out of interest: can you quote the part of the dissertation that you refer to? What you sometimes run into with regard to in-header vs. in-document is what happens when you store the document without it's response context. While the media type remains detectable (given proper rules/suffixes) headers are lost. I have had occasions where people wanted to put links in the document, too for that very reason. Jan Markus,
see your point and its a good one. Out of interest: can you quote the part of the dissertation that you refer to?

What you sometimes run into with regard to in-header vs. in-document is what happens when you store the document without it’s response context. While the media type remains detectable (given proper rules/suffixes) headers are lost. I have had occasions where people wanted to put links in the document, too for that very reason.

Jan

]]> By: mkarg http://www.nordsc.com/blog/?p=376#comment-95 mkarg Sun, 14 Feb 2010 18:42:41 +0000 http://www.nordsc.com/blog/?p=376#comment-95 My blog entry was about the dissertation, not about my opinion of usefulness. In fact, it is Fielding's dissertation that mandates that the state change links must be taken from the hypermedia. But frankly spoken, when thinking Fielding's idea to the end, I must agree with him, that it is always the correct solution: If your client is unable to get the links out of the document itself, the obviously the document format is either an improper choice for use in a hypermedia context (which REST is about), or the client seems to be badly coded (it seems to be Accept:-ing a data format that it actually cannot interpret correctly). See, if your browser is unable to understand links in PDFs, then it should not send Accept: text/pdf, obviously. No need to tweak around that by putting the links in the header -- fix it! ;-) My blog entry was about the dissertation, not about my opinion of usefulness. In fact, it is Fielding’s dissertation that mandates that the state change links must be taken from the hypermedia. But frankly spoken, when thinking Fielding’s idea to the end, I must agree with him, that it is always the correct solution: If your client is unable to get the links out of the document itself, the obviously the document format is either an improper choice for use in a hypermedia context (which REST is about), or the client seems to be badly coded (it seems to be Accept:-ing a data format that it actually cannot interpret correctly). See, if your browser is unable to understand links in PDFs, then it should not send Accept: text/pdf, obviously. No need to tweak around that by putting the links in the header — fix it! ;-)

]]>