<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="../assets/xml/rss.xsl" media="all"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Code and More - IT consultanancy, software development, and training in Cheshire (Posts about json)</title><link>https://www.codeandmore.co.uk/</link><description></description><atom:link href="https://www.codeandmore.co.uk/tags/json.xml" rel="self" type="application/rss+xml"></atom:link><language>en</language><copyright>Contents © 2025 &lt;a href="mailto:graeme@codeandmore.co.uk"&gt;Graeme Pietersz&lt;/a&gt; </copyright><lastBuildDate>Wed, 16 Apr 2025 15:44:05 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>When REST and Websockets are a bad idea</title><link>https://www.codeandmore.co.uk/posts/when-not-to-use-http/</link><dc:creator>Graeme Pietersz</dc:creator><description>&lt;div&gt;&lt;p&gt;HTTP was designed for a specific use case: communication between a browser and a server. The same is true for JSON. Is also often a good idea to use HTTP ports for things like mobile apps because a significant number of people need to use them from networks that block other ports (e.g. when using corporate wi-fi). The problem is that HTTP and websockets are used inappropriately.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://www.codeandmore.co.uk/posts/when-not-to-use-http/"&gt;Read more…&lt;/a&gt; (4 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><category>http</category><category>json</category><category>rest</category><category>web</category><category>websockets</category><guid>https://www.codeandmore.co.uk/posts/when-not-to-use-http/</guid><pubDate>Fri, 19 Apr 2019 10:58:20 GMT</pubDate></item></channel></rss>