http://simonwillison.net/2010-02-03T00:37:34+00:00Simon Willison2010-02-03T00:37:34+00:002010-02-03T00:37:34+00:00https://simonwillison.net/2010/Feb/3/scriptcommunicator/

<p><strong><a href="http://amix.dk/blog/post/19489#ScriptCommunicator-implementing-comet-long-polling-for-all-browse">Comet (long polling) for all browsers using ScriptCommunicator</a></strong></p> More Comet from the Plurk team: 80 lines of dependency free JavaScript implementing long polling using script tags (hence working cross-domain) across IE6+, Firefox, WebKit and Opera. The clever bit is the code to detect loading errors. It doesn’t try to fix the infinite loading indicator problem—is that still a cromulent usability concern? <p>Tags: <a href="https://simonwillison.net/tags/comet">comet</a>, <a href="https://simonwillison.net/tags/javascript">javascript</a>, <a href="https://simonwillison.net/tags/long-polling">long-polling</a>, <a href="https://simonwillison.net/tags/plurk">plurk</a>, <a href="https://simonwillison.net/tags/usability">usability</a></p>

2010-02-01T10:15:02+00:002010-02-01T10:15:02+00:00https://simonwillison.net/2010/Feb/1/distributed/

<p><strong><a href="http://amix.dk/blog/post/19386">Distributed lock on top of memcached</a></strong></p> A simple Python context manager (taking advantage of the with statement) that implements a distributed lock using memcached to store lock state: “memcached_lock can be used to ensure that some global data is only updated by one server”. Redis would work well for this kind of thing as well. <p>Tags: <a href="https://simonwillison.net/tags/concurrency">concurrency</a>, <a href="https://simonwillison.net/tags/contextmanager">contextmanager</a>, <a href="https://simonwillison.net/tags/locking">locking</a>, <a href="https://simonwillison.net/tags/memcached">memcached</a>, <a href="https://simonwillison.net/tags/plurk">plurk</a>, <a href="https://simonwillison.net/tags/python">python</a>, <a href="https://simonwillison.net/tags/redis">redis</a>, <a href="https://simonwillison.net/tags/with">with</a></p>

2010-02-01T10:13:14+00:002010-02-01T10:13:14+00:00https://simonwillison.net/2010/Feb/1/plurk/

<p><strong><a href="http://amix.dk/blog/post/19490">Plurk: Instant conversations using Comet</a></strong></p> Plurk’s comet implementation sounds pretty amazing. They’re using a single quad-core server with 32GB of RAM running 8 Node.js instances to serve long-polled comet to 100,000+ simultaneous users. They switched to Node from Java JBoss/Netty and found the new solution used 10 times less memory. <p><small></small>Via <a href="http://news.ycombinator.com/item?id=1088699">Hacker News</a></small></p> <p>Tags: <a href="https://simonwillison.net/tags/comet">comet</a>, <a href="https://simonwillison.net/tags/java">java</a>, <a href="https://simonwillison.net/tags/javascript">javascript</a>, <a href="https://simonwillison.net/tags/jboss">jboss</a>, <a href="https://simonwillison.net/tags/netty">netty</a>, <a href="https://simonwillison.net/tags/nodejs">nodejs</a>, <a href="https://simonwillison.net/tags/plurk">plurk</a></p>