Comments on: JSON mime-type

By: Mere Grand Mitsou

Mere Grand Mitsou — Tue, 25 May 2010 20:33:36 +0000

je suis très heureuse de la venue sur terre du petit adrien, un peu plus tôt que prévu, de quoi bousculer ses parents….! j’envoie des câlins-doudoune à mon petit-fils….

By: Tom

Tom — Thu, 04 Mar 2010 23:25:02 +0000

Funny, this helped me too

By: Joe

Joe — Thu, 08 Oct 2009 18:01:19 +0000

I have to agree with my esteemed peers Quinn and jonny, you have illuminated the dark cavern of JSON mime types with your own brilliance. Three cheers to you, comrade Barbieri and a sincere “Thank You”.

By: Quinn

Quinn — Sat, 04 Apr 2009 13:54:43 +0000

Let me second Jonny – this is exactly what I needed to know. (And it comes up first when you Google json mime-type, too.)

By: Jonny

Jonny — Thu, 26 Mar 2009 22:14:19 +0000

I think you are incorrect in your article here, primarily about this just being a reminder for you. Clearly this is not just a reminder for you because I googled “JSON MIME type” and this article came-up. I needed to finish my J2EE project and therefore needed a reminder for the JSON content-type header. I understand this is merely an empirical claim, but sufficient to counter your argument that this is just a reminder for you; it has in-fact helped me as well, and perhaps these other folks in your comments. You have inadvertently made the world a better place with this post without your fully being aware of the fact.

By: character

character — Sat, 06 Sep 2008 11:02:38 +0000

json.org says that it should be e.g. {“entity1″: “value”} instead of {entity1: “value”}.

By: Sergey Shepelev

Sergey Shepelev — Fri, 15 Aug 2008 15:55:33 +0000

Thanks.

By: aaron

aaron — Sun, 09 Dec 2007 06:12:56 +0000

good!