<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Web on Nikhil&#39;s blog</title>
    <link>https://master--suspicious-stonebraker-7d2d21.netlify.app/tags/web/</link>
    <description>Recent content in Web on Nikhil&#39;s blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-US</language>
    <lastBuildDate>Thu, 22 Dec 2011 23:37:00 +0000</lastBuildDate>
    <atom:link href="https://master--suspicious-stonebraker-7d2d21.netlify.app/tags/web/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Tic-Tac-Toe with Redis and Backbone.js</title>
      <link>https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2011/tic-tac-toe-with-redis-and-backbonejs/</link>
      <pubDate>Thu, 22 Dec 2011 23:37:00 +0000</pubDate>
      <guid>https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2011/tic-tac-toe-with-redis-and-backbonejs/</guid>
      <description>This post is a technical overview of my Tic-Tac-Toe implementation. It is a zero server-side logic, pub-sub based, realtime, multiplayer game which uses Redis and Backbone as the key enablers of real-time and moving logic to the client side, respectively. Now that all the buzz-words are out of the way, the source code is on Github. There are rough edges with reliable communication, security holes do exist, but for the most part it works well.</description>
    </item>
    <item>
      <title>QHttpServer: Web Apps in Qt</title>
      <link>https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2011/qhttpserver-web-apps-in-qt/</link>
      <pubDate>Sun, 06 Feb 2011 10:46:00 +0000</pubDate>
      <guid>https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2011/qhttpserver-web-apps-in-qt/</guid>
      <description>Qt is a great GUI toolkit, but it is also an entire C++ standard library waiting to be used for other tasks. In addition the network module is really powerful. I&amp;#8217;ve been playing around with node.js for a while now, and realized that Qt&amp;#8217;s default asynchronous nature maps over perfectly to create a event-based web server. To make things better, Ryan Dahl&amp;#8217;s small and fast http-parser is freely available. So I just combined the two, and here is QHttpServer.</description>
    </item>
    <item>
      <title>The Secret Question System is insecure</title>
      <link>https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2007/secret-question-system-is-insecure/</link>
      <pubDate>Thu, 12 Jul 2007 23:20:00 +0000</pubDate>
      <guid>https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2007/secret-question-system-is-insecure/</guid>
      <description>Seeing that this is so obvious and easily breakable, I&#39;m surprised sites still continue to use the secret question to recover your password. The problem is not so much in the system as in the questions chosen. A really secret question would be one which is known to you and only to you. But usually secret questions involve your mother&#39;s maiden name, or your pet or childhood hero. Now to anyone who has known you for a sufficient amount of time, and anyone who has read your profile on one of the social networking sites you are a member of, these are easily answerable.</description>
    </item>
  </channel>
</rss>
