<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Javascript on Daniel Pomfret</title>
    <link>https://pomfret.uk/tags/javascript/</link>
    <description>Recent content in Javascript on Daniel Pomfret</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <copyright>© Daniel Pomfret</copyright>
    <lastBuildDate>Wed, 11 Jan 2017 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://pomfret.uk/tags/javascript/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Querying Source Servers with PHP : Part 2</title>
      <link>https://pomfret.uk/posts/querying-source-servers-php-part-2/</link>
      <pubDate>Wed, 11 Jan 2017 00:00:00 +0000</pubDate>
      <guid>https://pomfret.uk/posts/querying-source-servers-php-part-2/</guid>
      <description>&lt;p&gt;So I have my JSON data which contains all the query information which was returned from the Source Query Protocol. I&amp;rsquo;m storing it as a flat JSON file - the reason being (as discussed in my &lt;a href=&#34;https://pomfret.uk/posts/querying-source-servers-php-part-1/&#34;&gt;last post&lt;/a&gt;) is simply due to speed (or the assumption it would be faster). I don&amp;rsquo;t want to be getting into caching database queries, optimising the indexes, normalisation etc&amp;hellip; As this project is for fun, let&amp;rsquo;s just store the JSON on the file system, and pull the data out when we need it.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
