A place to cache linked articles (think custom and personal wayback machine)
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

12345
  1. title: WebSockets connection to scripting.com
  2. url: http://scripting.com/liveblog/users/davewiner/2015/11/30/0510.html
  3. hash_url: 8ed0a0bf4fc4d4051e4c075fc3a3921c
  4. <p>Last week I <a href="http://scripting.com/liveblog/users/davewiner/2015/11/23/0410.html">posted</a> the first update on 1999.io, the software I'm using to write this blog. It's coming along well, so it's time for a second update.</p><p><span>This update is for the programmers, although if you're not a programmer, you're totally welcome to listen in.</span></p><p><b>It's a floor wax <i>and</i> a dessert topping!</b></p><p>Remember that old SNL skit for Shimmer that's a <a href="https://screen.yahoo.com/shimmer-floor-wax-000000185.html">floor wax</a> that's also a dessert topping? Well 1999.io is like that. It's a blogging tool, but it's also a chat application. In fact it started as a chat app, and it became a blogging app. Basically because, as you know, everything I work on eventually becomes a blogging app. It's what I do.&nbsp;</p><p>And I also like to create developer toolkits to show others how they can plug into my work, and that's what I'd like to show off today.&nbsp;</p><p><b>A demo app</b></p><p>Here's a <a href="http://fargo.io/code/websockets3/test1999.html">web page</a> that contains a JavaScript app that's designed to run in the browser.</p><p>It opens a WebSockets connection with the 1999.io server, asking to listen to all the updates for the <i>scripting</i> channel.&nbsp;</p><p>When I post something new on this blog, or someone posts or updates a comment, you'll be notified, and will get a copy of the JSON source for the post.&nbsp;</p><p>You can try it out by posting a comment under this post. Modify it whenever you want to see something happen in the demo app.</p><p><b>Notes</b></p><p></p><ol><li><span>The code is running in the browser, but it could just as easily run on a server, in Node.js.</span></li><li><span>The thing to observer is how instantaneous it is (that is if everything is working, knock wood).</span></li><li><span>Here's the <a href="https://github.com/scripting/1999client">GitHub repository</a> containing the source.&nbsp;</span></li><li>And here's a <a href="https://github.com/scripting/1999client/blob/master/code.js#L81">bookmark</a> for the place in the code where it gets interesting.&nbsp;</li></ol><p></p>