<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Disqus - Latest Comments for skywalk</title><link>http://disqus.com/by/skywalk/</link><description></description><atom:link href="http://disqus.com/skywalk/comments.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Thu, 21 Nov 2013 20:32:31 -0000</lastBuildDate><item><title>Re: Joey Guerra</title><link>http://blog.joeyguerra.com/content-negotiation-in-node-js-augmenting-express-js#comment-1133841294</link><description>&lt;p&gt;The spec just describes the protocol and gives guidance on implementation. It's not like implementation is mandated or expected. It seems like the easiest thing to do is pop a 406 on anything other than the format my feature calls for unless I have a reason to do otherwise, because of this reason, also from the spec:&lt;/p&gt;&lt;p&gt;3. It complicates the implementation of an origin server and the&lt;br&gt;         algorithms for generating responses to a request.&lt;/p&gt;&lt;p&gt;The main point I was trying to make was that I feel a generic solution for this, which is the only thing that would make it approachable at all from a business/time perspective, will eventually run into some edge cases. On top of that, I have to use whatever technology said generic solution(s) are built on.&lt;/p&gt;&lt;p&gt;I'm not saying this strategy is useless, I can think of some cases where it actually would add some value, too. I just don't see usefulness in the generic sense covering "all websites". Most of the hang-ups that come to mind involve input/forms. Then there's the SPA, making all those ajax calls for JSON data. Do I really need to spend time making an HTML representation of that endpoint? What's the value there?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jonathan Keith</dc:creator><pubDate>Thu, 21 Nov 2013 20:32:31 -0000</pubDate></item><item><title>Re: Joey Guerra</title><link>http://blog.joeyguerra.com/content-negotiation-in-node-js-augmenting-express-js#comment-1129196742</link><description>&lt;p&gt;Good arguments, but to counter, it seems like a feature that can only be made generic for the common case. For example, even with such a solution, once you get outside of one model per page, you're in trouble. Someone is off implementing 4 different views or formatters for each model and content type for every page like this while someone else ships countless new html-only features to prod.&lt;/p&gt;&lt;p&gt;The main phrase I take issue with is "every website". There has to be some reason that most sites, including any I've ever been asked to build, don't do this. Does the &lt;a href="http://True.com" rel="nofollow noopener" target="_blank" title="True.com"&gt;True.com&lt;/a&gt; sign-up page really need a JSON, XML, and CSV representation? I think we've run into 'delivery &amp;gt; ideal perfection' again.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jonathan Keith</dc:creator><pubDate>Tue, 19 Nov 2013 01:10:08 -0000</pubDate></item><item><title>Re: 105.3 The FAN - Stars Find Scoring From Unexpected Places In 5-4 OT Win Over Red Wings</title><link>http://www.1053thefan.com/Stars-Find-Scoring-From-Unexpected-Places-In-5-4-O/3650366#comment-5113142</link><description>&lt;p&gt;Amazing game and a great recap. Keep it up Stars! (...and you too, Jay)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jonathan Keith</dc:creator><pubDate>Wed, 14 Jan 2009 10:15:07 -0000</pubDate></item></channel></rss>