FEED Validator

Congratulations!

This is a valid Atom 1.0 feed.

Recommendations

This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.

• line 97, column 0: content should not contain data-lang attribute (4 occurrences) [help]

  <div class="highlight"><pre><code class="langu ...
  

• line 324, column 0: content should not contain script tag (2 occurrences) [help]

      <script src="http://gist.github.com/25675.js"></scrip ...
  

• line 516, column 37: Two entries with the same value for atom:updated: 2008-05-22T00:00:00+00:00 [help]

     <updated>2008-05-22T00:00:00+00:00</updated>
                                       ^

Source: http://saladwithsteve.com/atom.xml

1. <?xml version="1.0" encoding="utf-8"?>
2. <feed xmlns="http://www.w3.org/2005/Atom">
3. <title>saladwithsteve</title>
4. <link href="http://saladwithsteve.com/atom.xml" rel="self"/>
5. <link href="http://saladwithsteve.com/" rel="alternate"/>
6. <updated>2015-02-10T18:09:20+00:00</updated>
7. <id>http://saladwithsteve.com/</id>
8. <author>
9.   <name>Steve Jenson</name>
10.   <email>stevej@fruitless.org</email>
11. </author>
13. <entry>
14.   <title>Building F# on Mac OS X</title>
15.   <link href="http://saladwithsteve.com/2010/07/building-fsharp-on-the-mac.html"/>
16.   <updated>2010-07-22T00:00:00+00:00</updated>
17.   <id>http://saladwithsteve.com/2010/07/building-fsharp-on-the-mac.html</id>
18.   <content type="html">&lt;p&gt;I&amp;#8217;m attending the Emerging Languages Conference here in Portland,
19. OR, where I ran into Joe Pamer on the F# team. I’ve been following F#
20. for a while but have had trouble running it on the Mac.</p>
21. <p>Joe says his team at Microsoft runs into these issues often with users
22. and was kind enough to walk me through the steps to get F# running on
23. the mac.</p>
24. <p>First install Mono, there’s a <a href="http://www.go-mono.com/mono-downloads/download.html">dmg</a></p>
25. <p>1. Download the <a href="http://fsxplat.codeplex.com/SourceControl/list/changesets">zip file</a>
26. 2. Run <code>make_package.sh</code></p>
27. <p>This will complain about not finding <code>dpkg-buildpackage</code> but the dll will be signed with the mono key and be ready to use.</p>
28. <p><tt>
29. Assembly bin/FSharp.Core.dll signed. <br />
30. ./make_package.sh: line 19: dpkg-buildpackage: command not found
31. </tt></p>
32. <p>Now run <code>gacutil</code> which will install the assembly into mono’s library path.</p>
33. <p><tt>
34. sudo gacutil -i ./fsharp/bin/FSharp.Core.dll
35. </tt></p>
36. <p>And now you’re ready to write some programs! There are some known
37. bugs around how it interacts with mono winforms (I think that’s a
38. thing, it’s greek to me) so we’ll turn that off.</p>
39. <p>Now let’s fire up the repl, run an expression, and exit.</p>
40. <p><tt>
41. $ mono fsharp/bin/fsi.exe <del>-gui</del> <br />
42. Microsoft® F# 2.0 Interactive build 2.0.0.0<br />
43. Copyright © Microsoft Corporation. All Rights Reserved. <br />
44. For help type #help;; <br />
45. > printf “hi\n”;; <br />
46. hi <br />
47. val it : unit = () <br />
48. > #q;;<br />
49. <br />
50. - Exit…<br />
51. </tt></p>
52. &lt;p&gt;Joe says that they are working on getting DMGs up for Mac users &lt;span class=&quot;caps&quot;&gt;ASAP&lt;/span&gt;. (within days)&lt;/p&gt;</content>
53.   <author>
54.     <name>Steve Jenson</name>
55.     <uri>http://saladwithsteve.com/about.html</uri>
56.   </author>
57. </entry>
59. <entry>
60.   <title>Hello Again!</title>
61.   <link href="http://saladwithsteve.com/2010/05/hello-again.html"/>
62.   <updated>2010-05-21T00:00:00+00:00</updated>
63.   <id>http://saladwithsteve.com/2010/05/hello-again.html</id>
64.   <content type="html">&lt;h1&gt;Hello Again!&lt;/h1&gt;
65. <p>I’ve changed some things around here.</p>
66. <p>This site is now generated with
67. <a href="http://github.com/stevej/jekyll">Jekyll</a></p>
68. <p>Switching from Blogger wasn’t an easy decision but I felt like it was
69. time to jump start things and make it fun to write and tinker here
70. again.</p>
71. <p>Something that didn’t make the conversion were all of the old
72. comments. Jekyll doesn’t support comments. I considered porting them
73. over statically but I had already sat on the conversion for 6 months
74. and was ready to move on. See, I actually switched back in December
75. but had never actually updated this version of the site.</p>
76. <p>People left many wonderful comments. In the future, I’d like to
77. encourage you to simply email me. My email address is in the ‘About
78. Me’ page linked at the top. If you’d like me to post your response,
79. let me know.</p>
80. <p>Oh, you can also see a mirror of all my content on the blog’s <a href="http://github.com/stevej/saladwithsteve">github
81. repo&lt;/a&gt;&lt;/p&gt;</content>
82.   <author>
83.     <name>Steve Jenson</name>
84.     <uri>http://saladwithsteve.com/about.html</uri>
85.   </author>
86. </entry>
88. <entry>
89.   <title>Higher Order Select in Ruby</title>
90.   <link href="http://saladwithsteve.com/2009/12/higher-order-select-in-ruby.html"/>
91.   <updated>2009-12-13T00:00:00+00:00</updated>
92.   <id>http://saladwithsteve.com/2009/12/higher-order-select-in-ruby.html</id>
93.   <content type="html">&lt;h1&gt;Higher Order Select in Ruby&lt;/h1&gt;
94. <p>When I was converting my blog to jekyll, I had to write a nested
95. select in Ruby and found it to be a little painful.</p>
96. <p>In Ruby:</p>
97. <div class="highlight"><pre><code class="language-ruby" data-lang="ruby"><span class="c1"># For a given feed, return all the entries that</span>
98. <span class="c1"># are blog posts rather than templates, etc.</span>
99. <span class="k">def</span> <span class="nf">posts</span><span class="p">(</span><span class="n">feed</span><span class="p">)</span>
100.  <span class="c1"># The post must have a category of type #post</span>
101.  <span class="n">feed</span><span class="o">.</span><span class="n">entries</span><span class="o">.</span><span class="n">select</span> <span class="k">do</span> <span class="o">|</span><span class="n">entry</span><span class="o">|</span>
102.    <span class="o">!</span><span class="n">entry</span><span class="o">.</span><span class="n">categories</span><span class="o">.</span><span class="n">select</span> <span class="k">do</span> <span class="o">|</span><span class="n">c</span><span class="o">|</span>
103.      <span class="n">c</span><span class="o">.</span><span class="n">term</span> <span class="o">==</span> <span class="s1">'http://schemas.google.com/blogger/2008/kind#post'</span>
104.    <span class="k">end</span><span class="o">.</span><span class="n">empty?</span>
105.  <span class="k">end</span>
106. <span class="k">end</span></code></pre></div><p>In Scala, things are a little simpler thanks to anaphora: the ability
107. to easily reference earlier state implicitly. That’s what the _ means
108. in this context.</p>
109. <div class="highlight"><pre><code class="language-scala" data-lang="scala"><span class="n">feed</span><span class="o">.</span><span class="n">entries</span><span class="o">.</span><span class="n">filter</span><span class="o">(!</span><span class="k">_</span><span class="o">.</span><span class="n">categories</span><span class="o">.</span><span class="n">filter</span><span class="o">(</span><span class="k">_</span><span class="o">.</span><span class="n">term</span> <span class="o">==</span> <span class="s">"http://schemas.google.com/blogger/2008/kind#post"</span><span class="o">).</span><span class="n">isEmpty</span><span class="o">)</span></code></pre></div><p>Imagine the following sentence in English: “Steve used Steve’s keys to
110. start Steve’s car”. Most programming languages insist on that level of
111. verbosity.</p>
112. &lt;p&gt;Raganwald has a nice &lt;a href=&quot;http://github.com/raganwald/homoiconic/blob/master/2009-09-22/anaphora.md#readme&quot;&gt;piece&lt;/a&gt; exploring Anaphora in Ruby.&lt;/p&gt;</content>
113.   <author>
114.     <name>Steve Jenson</name>
115.     <uri>http://saladwithsteve.com/about.html</uri>
116.   </author>
117. </entry>
119. <entry>
120.   <title>Functional Refactoring</title>
121.   <link href="http://saladwithsteve.com/2009/07/functional-refactoring-1-replace.html"/>
122.   <updated>2009-07-21T00:00:00+00:00</updated>
123.   <id>http://saladwithsteve.com/2009/07/functional-refactoring-1-replace.html</id>
124.   <content type="html">&lt;p&gt;
125.    Recently, while working on some code, I noticed that I have been making the same transform on lots of functional code in Scala. I think it's clearly a Refactoring and should have a name.
126.    </p>
127.  
128.    <p>
129.    <h4>"Replace conditional inside fold with filter"</h4>
130.    </p>
131.  
132.    <p>
133.    The idea is that if you're folding over items in a list and manipulating them based on a conditional, it might be clearer if you pull out the conditional and filter the list on that conditional first.
134.    </p>
135.    <p>
136.    Here is a contrived example borrowed from a fake test suite. Let's say I had code with a conditional inside of a fold:
137.    </p>
138.    <p>
139.    <div class="highlight"><pre><code class="language-scala" data-lang="scala"><span class="n">sampleUsers</span><span class="o">.</span><span class="n">values</span><span class="o">.</span><span class="n">foreach</span> <span class="o">{</span> <span class="n">u</span> <span class="k">=></span>
140.      <span class="k">if</span> <span class="o">(</span><span class="n">u</span><span class="o">.</span><span class="n">id</span> <span class="o">!=</span> <span class="mi">0</span><span class="o">)</span> <span class="o">{</span>
141.        <span class="nc">Authentication</span><span class="o">(</span><span class="n">u</span><span class="o">.</span><span class="n">id</span><span class="o">,</span> <span class="n">u</span><span class="o">.</span><span class="n">hash</span><span class="o">).</span><span class="n">passwordToken</span> <span class="n">mustEqual</span> <span class="n">u</span><span class="o">.</span><span class="n">passwordToken</span>
142.      <span class="o">}</span>
143.    <span class="o">}</span></code></pre></div>
144.    </p>
145.    <p>
146.    Let's apply this refactoring to make the test case clearer.
147.    </p>
148.    <p>
149.      <div class="highlight"><pre><code class="language-scala" data-lang="scala"><span class="n">sampleUsers</span><span class="o">.</span><span class="n">values</span><span class="o">.</span><span class="n">filter</span><span class="o">(</span><span class="n">u</span> <span class="k">=></span> <span class="n">u</span><span class="o">.</span><span class="n">id</span> <span class="o">!=</span> <span class="mi">0</span><span class="o">).</span><span class="n">foreach</span> <span class="o">{</span> <span class="n">u</span> <span class="k">=></span>
150.      <span class="nc">Authentication</span><span class="o">(</span><span class="n">u</span><span class="o">.</span><span class="n">id</span><span class="o">,</span> <span class="n">u</span><span class="o">.</span><span class="n">hash</span><span class="o">).</span><span class="n">passwordToken</span> <span class="n">mustEqual</span> <span class="n">u</span><span class="o">.</span><span class="n">passwordToken</span>
151.    <span class="o">}</span></code></pre></div>
152.    </p>
153.    <p>
154.    This works with multiple inner conditionals as well. You can fit them into one filter or chain multiple filters together.
155.    </p>
156.    <p>
157.    Even though this is a simple refactoring, it seems like a worthwhile place to start cataloging.
158.    </p>
159. </content>
160.   <author>
161.     <name>Steve Jenson</name>
162.     <uri>http://saladwithsteve.com/about.html</uri>
163.   </author>
164. </entry>
166. <entry>
167.   <title>More Varnish Thoughts from the Author</title>
168.   <link href="http://saladwithsteve.com/2008/12/more-varnish-thoughts-from-author.html"/>
169.   <updated>2008-12-09T00:00:00+00:00</updated>
170.   <id>http://saladwithsteve.com/2008/12/more-varnish-thoughts-from-author.html</id>
171.   <content type="html">&lt;a href=&quot;http://people.freebsd.org/~phk/&quot;&gt;Poul-Henning Kamp&lt;/a&gt;, the lead author of Varnish, was kind enough to respond to my blog post.
172.  
173.    <tt>
174.    <p>
175.    Hi Steve,
176.    </p>
177.    <p>
178.    I read your comments about Varnish and thought I'd better explain
179.    myself, feel free to post this if you want.
180.    </p>
181.    <p>
182.    The reason why we don't multiplex threads in Varnish is that it has
183.    not become a priority for us yet, and I am not convinced that we
184.    will ever see it become a priority at the cost it bears.
185.    </p>
186.    <p>
187.    A common misconception is that varnish parks a thread waiting for
188.    the client to send the next request.  We do not, that would be
189.    horribly stupid.  Sessions are multiplexed when idle.
190.    </p>
191.    <p>
192.    The Varnish worker thread takes over when the request is completely
193.    read and leaves the session again when the answer is delivered to
194.    the network stack (and no further input is pending).
195.    </p>
196.    <p>
197.    For a cache hit, this takes less than 10 microseconds, and we are
198.    still shaving that number.
199.    </p>
200.    <p>
201.    The problem about multiplexing is that it is horribly expensive,
202.    both in system calls, cache pressure and complexity.
203.    </p>
204.    <p>
205.    If we had a system call that was called "write these bytes, but
206.    don't block longer than N seconds", multiplexing could be sensibly
207.    implemented.
208.    </p>
209.    <p>
210.    But with POSIX mostly being a historical society, it will cost you
211.    around 7 system calls, some surprisingly expensive, to even find
212.    out if multiplexing is necessary in the first place.
213.    </p>
214.    <p>
215.    In comparison, today Varnish delivers a cache-hit in 7 system calls
216.    *total* of which a few are technically only there for debugging.
217.    </p>
218.    <p>
219.    The next good reason is that we have no really fiddled with the
220.    sendbuffer sizes yet, but obviously, if you sendbuffer can swallow
221.    the read, the thread does not wait.
222.    </p>
223.    <p>
224.    And if that fails, a thread blocked in a write(2) system call is
225.    quite cheap to have around.
226.    </p>
227.    <p>
228.    It uses a little RAM, but it's not that much, and we can probably
229.    tune it down quite a bit.
230.    </p>
231.    <p>
232.    The scheduler does not bother more with the thread than it has to,
233.    and when it does, the VM hardware system is not kickstarted every
234.    time we cross the user/kernel barrier.
235.    </p>
236.    <p>
237.    Without getting into spectroscoping comparisons between apples and
238.    oranges, a thread just lounging around, waiting for the network
239.    stack to do its thing, is much, much cheaper than a thread which
240.    does a lot of system calls and fd-table walking, only to perform
241.    a few and small(-ish) writes every time the network stack wakes up.
242.    </p>
243.    <p>
244.    And the final reason why it may never become necessary to multiplex
245.    threads, is that servers are cheap.
246.    </p>
247.    <p>
248.    But if we get to the point where we need multiplexing, we will do
249.    it.
250.    </p>
251.    <p>
252.    But I like the old design principles from the X11 project: we will
253.    not do it, until we have a server that doesn't work without it.
254.    </p>
255.    <p>
256.    But if you are in the business of delivering ISOs to 56k modems
257.    then yes, Varnish is probably not for you.
258.    </p>
259.    <p>
260.    Poul-Henning
261.    </p>
262.    </tt>
263. </content>
264.   <author>
265.     <name>Steve Jenson</name>
266.     <uri>http://saladwithsteve.com/about.html</uri>
267.   </author>
268. </entry>
270. <entry>
271.   <title>Thoughts on Varnish</title>
272.   <link href="http://saladwithsteve.com/2008/12/thoughts-on-varnish.html"/>
273.   <updated>2008-12-07T00:00:00+00:00</updated>
274.   <id>http://saladwithsteve.com/2008/12/thoughts-on-varnish.html</id>
275.   <content type="html">&lt;p&gt;&lt;a href=&quot;http://varnish.projects.linpro.no/&quot;&gt;Varnish&lt;/a&gt; is getting a lot of attention these days around the internet, and with good reason, it&amp;#8217;s a nicely written and speedy cache, and has a nice &lt;span class=&quot;caps&quot;&gt;DSL&lt;/span&gt; for caching. It has great features like hot reloading of cache rules and &lt;span class=&quot;caps&quot;&gt;ESI&lt;/span&gt;.&lt;/p&gt;
276.  
277.  
278.    <p>One thing that’s really surprised me, though, is that Varnish uses one thread per connection. Most network programs designed for high number of connection don’t use one thread per connection anymore as it has serious drawbacks.</p>
279.  
280.  
281.    <p>With slow clients, many of your threads are spending a lot of time doing nothing but blocking in <tt>write()</tt>. In all internet consumer apps, I believe, slow clients make up the majority of your connections. But even though the threads are doing nothing, the OS still has memory and scheduling overhead in dealing with them. You find yourself with an artificially low ceiling on the amount of users you can service with a single machine.</p>
282.  
283.    <p>What makes a client slow, though? Both speed and latency. Cell phones, 56k modems, and users on high speed links but not geographically close to your data center can all be classified as ‘slow’.</p>
284.  
285.  
286.    <p>One design that is more appropriate for dealing with the slow client problem uses a pool of worker
287.    threads or processes behind the scene and
288.    <a href="http://www.xmailserver.org/linux-patches/nio-improve.html">epoll</a> /
289.    <a href="http://people.freebsd.org/~jlemon/kqueue_slides/index.html">kqueue</a> / <a href="http://developers.sun.com/solaris/articles/event_completion.html">event
290.    ports</a> handling slow clients and
291.    telling the pool of workers that a socket is ready with a change notification. Your cost is still
292.    correlated with growth but at a much lower rate and the number of users you can service will
293.    dramatically increase.</p>
294.  
295.    <p>So why does Varnish use this older, more troublesome model? Probably because most services aren’t
296.    going to notice the bottleneck; They simply don’t have enough concurrent connections to worry about
297.    using a few extra machines. If you’re never saturated a load balancer or firewall, you’ve probably
298.    never had to seriously consider the <a href="http://www.kegel.com/c10k.html">C10k</a> issues involved.</p>
299.  
300.  
301.    <p>Also, unfortunately, the way most people write load tests is that they are only testing the All Fast
302.    Clients scenario and not a mix of fast clients and slow clients. I’m guilty of this, too.</p>
303.  
304.  
305.    <p>My executive summary: Varnish is a nice piece of software, and I hope they spend the time to make it
306.    useful for larger sites as well as smaller ones.</p>
307. </content>
308.   <author>
309.     <name>Steve Jenson</name>
310.     <uri>http://saladwithsteve.com/about.html</uri>
311.   </author>
312. </entry>
314. <entry>
315.   <title>More RPMs means faster access times. No news there.</title>
316.   <link href="http://saladwithsteve.com/2008/11/more-rpms-means-faster-access-times-no.html"/>
317.   <updated>2008-11-18T00:00:00+00:00</updated>
318.   <id>http://saladwithsteve.com/2008/11/more-rpms-means-faster-access-times-no.html</id>
319.   <content type="html">&lt;p&gt;
320.    When I upgraded my home laptop from a 2-year old MacBook Pro to one of the newly released unibody models, I decided to upgrade from a 5400 RPM drive to a 7200 RPM drive. I ran some <a href="http://code.google.com/p/bonnie-64/">bonnie-64</a> benchmarks and noticed a 40% improvement in random seeks/sec and some other impressive numbers. It's helped make my weekend hacking much more pleasant.
321.    </p>
322.    <p>
323.    Here are the old numbers:
324.    <script src="http://gist.github.com/25675.js"></script>
325.    </p>
326.    <p>
327.    and the new numbers:
328.    <script src="http://gist.github.com/25200.js"></script>
329.    </p>
330.    <p>
331.    <strong>Bottom line: Recommended</strong>
332.    </p>
333. </content>
334.   <author>
335.     <name>Steve Jenson</name>
336.     <uri>http://saladwithsteve.com/about.html</uri>
337.   </author>
338. </entry>
340. <entry>
341.   <title>Amazon as Political Pulpit</title>
342.   <link href="http://saladwithsteve.com/2008/09/amazon-as-political-pulpit.html"/>
343.   <updated>2008-09-13T00:00:00+00:00</updated>
344.   <id>http://saladwithsteve.com/2008/09/amazon-as-political-pulpit.html</id>
345.   <content type="html">&lt;p&gt;
346.    Check out the <a href="http://www.amazon.com/review/product/B000FKBCX4/ref=dp_db_cm_cr_acr_txt?_encoding=UTF8&showViewpoints=1">Amazon reviews for Spore</a>, the new Will Wright game. 2,016 of the 2216 reviews gave it 1 star for the heavy-handed DRM. I use Amazon reviews heavily and I've never seen protest brought to the reviews at this scale before. Let's see if people take notice.
347.    </p>
348.    <p>
349.    <a href="http://torrentfreak.com/spore-most-pirated-game-ever-thanks-to-drm-080913/">TorrentFreak</a> points out the following:
350.    <blockquote>DRM doesn’t stop people from pirating a game, on the contrary. It only hurts legitimate customers since the DRM is removed from the pirate version."</blockquote>
351.    </p>
352.    <p>There are lots of philosophical reasons not to buy things with DRM. For me, the practical reason wins out. I'd rather deal with having to store music CDs and not play some potentially awesome games than deal with losing my data due to short-sighted DRM.
353.    </p>
354. </content>
355.   <author>
356.     <name>Steve Jenson</name>
357.     <uri>http://saladwithsteve.com/about.html</uri>
358.   </author>
359. </entry>
361. <entry>
362.   <title>Alex's Scala Talk at C4[2]</title>
363.   <link href="http://saladwithsteve.com/2008/09/alexs-scala-talk-at-c42.html"/>
364.   <updated>2008-09-12T00:00:00+00:00</updated>
365.   <id>http://saladwithsteve.com/2008/09/alexs-scala-talk-at-c42.html</id>
366.   <content type="html">&lt;a href=&quot;http://al3x.net/&quot;&gt;al3x&lt;/a&gt; gave a &lt;a href=&quot;http://www.slideshare.net/al3x/why-scala-presentation/&quot;&gt;talk on Scala&lt;/a&gt; recently at &lt;a href=&quot;http://rentzsch.com/c4/twoOpen/&quot;&gt;C4[2]&lt;/a&gt; and it hits a lot of the high points as to why we're using Scala at Twitter to build back-end services. I've been programming in Scala seriously for about a year and a half now and it's positively ruined me for plain Java.
367. </content>
368.   <author>
369.     <name>Steve Jenson</name>
370.     <uri>http://saladwithsteve.com/about.html</uri>
371.   </author>
372. </entry>
374. <entry>
375.   <title>So I don't forget it.</title>
376.   <link href="http://saladwithsteve.com/2008/07/so-i-dont-forget-it.html"/>
377.   <updated>2008-07-30T00:00:00+00:00</updated>
378.   <id>http://saladwithsteve.com/2008/07/so-i-dont-forget-it.html</id>
379.   <content type="html">A cheesy generic tcp proxy I found cruising the webs built out of &lt;code&gt;netcat&lt;/code&gt;, &lt;code&gt;fifo&lt;/code&gt;s, and &lt;code&gt;tee&lt;/code&gt;:
380.  
381.    <p>
382.    <code>
383.    $ mkfifo backpipe<br />
384.    $ sudo nc -l 80 0<backpipe | tee -a inflow | nc localhost 8080| tee -a outflow 1>backpipe
385.    </code>
386.    </p>
387.    This way you can also look at <code>inflow</code> and <code>outflow</code> to see what the actual contents were of the transaction.
388. </content>
389.   <author>
390.     <name>Steve Jenson</name>
391.     <uri>http://saladwithsteve.com/about.html</uri>
392.   </author>
393. </entry>
395. <entry>
396.   <title>Simulating Byzantine failure with SIGSTOP</title>
397.   <link href="http://saladwithsteve.com/2008/06/simulating-byzantine-failure-with.html"/>
398.   <updated>2008-06-30T00:00:00+00:00</updated>
399.   <id>http://saladwithsteve.com/2008/06/simulating-byzantine-failure-with.html</id>
400.   <content type="html">&lt;p&gt;
401.    If your service relies on connecting to an internal network server and
402.    that server isn't accepting connections, your client will obviously throw an
403.    error. This happens often enough that you probably already check for this and do the right thing in your various projects. But what if the server is accepting connections but never
404.    returning any data? This failure case is rare but very deadly.  Chet
405.    mentioned that you could simulate this using <tt>SIGSTOP</tt> so I
406.    decided to whip up an experiment with <tt>memcached</tt> as my victim.
407.    </p>
408.    <p>
409.    <pre>
410.    stevej@t42p:~$ ps auxww |grep memcache
411.    stevej    3451  0.0  0.0   2928  1872 pts/0    T    01:21   0:00 memcached -vv -p 11211
412.    stevej@t42p:~$ kill -stop 3451
413.    </pre>
414.    </p>
415.    <p>
416.    In another terminal:
417.    </p>
418.    <p>
419.    <pre>
420.    stevej@t42p:~$ irb
421.    irb(main):001:0> require 'rubygems'
422.    => true
423.    irb(main):002:0> require 'memcache'
424.    => true
425.    irb(main):003:0> CACHE = MemCache.new "localhost:11211"
426.    => <MemCache: 1 servers, 1 buckets, ns: nil, ro: false>
427.    irb(main):004:0> CACHE.get("foo")
428.    </pre>
429.    </p>
430.    <p>
431.    The client library happily hung for several hours while I did other
432.    things. How can a process that's suspended not timeout incoming
433.    connections?  Well, it's the kernel that services network requests and
434.    the process itself is only reading the buffers. If you want proof,
435.    look at this tcpdump output. Remember, the process has already been
436.    suspended by the time I ran tcpdump here.
437.    </p>
438.    <p>
439.    <pre>
440.    stevej@t42p:~$ sudo tcpdump -i lo port 11211
441.    tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
442.    listening on lo, link-type EN10MB (Ethernet), capture size 96 bytes
443.    18:02:40.576255 IP localhost.48124 > localhost.11211: F 2018798159:2018798159(0) ack 2012359105 win 257 <nop,nop,timestamp 15455978 14281170>
444.    18:02:40.577037 IP localhost.11211 > localhost.48124: . ack 1 win 256 <nop,nop,timestamp 15455979 15455978>
445.    18:03:19.037410 IP localhost.35662 > localhost.11211: S 2731273926:2731273926(0) win 32792 <mss 16396,sackOK,timestamp 15465593 0,nop,wscale 7>
446.    18:03:19.037435 IP localhost.11211 > localhost.35662: S 2723119696:2723119696(0) ack 2731273927 win 32768 <mss 16396,sackOK,timestamp 15465593 15465593,nop,wscale 7>
447.    18:03:19.037449 IP localhost.35662 > localhost.11211: . ack 1 win 257 <nop,nop,timestamp 15465593 15465593>
448.    18:03:19.037768 IP localhost.35662 > localhost.11211: P 1:10(9) ack 1 win 257 <nop,nop,timestamp 15465593 15465593>
449.    18:03:19.037776 IP localhost.11211 > localhost.35662: . ack 10 win 256 <nop,nop,timestamp 15465593 15465593>
450.    </pre>
451.    </p>
452.    <p>
453.    So a connect timeout wouldn't help here, you need a recv timeout or
454.    something else. Restarting your client process won't help at all,
455.    it'll simply get stuck in the same place. In Ruby, the easiest thing
456.    to do is to use the Timeout module. Sadly, it only has second
457.    granularity but that's a lot better than hanging for several
458.    hours. You can also set use Socket#setsockopt with a recv timeout if
459.    you need finer grained timeout resolution.
460.    </p>
461.    <p>
462.    <pre>
463.    stevej@t42p:~$ irb
464.    irb(main):001:0> require 'rubygems'
465.    => true
466.    irb(main):002:0> require 'memcache'
467.    => true
468.    irb(main):003:0> CACHE = MemCache.new "localhost:11211"
469.    => <MemCache: 1 servers, 1 buckets, ns: nil, ro: false>
470.    irb(main):004:0> require 'timeout'
471.    => false
472.    irb(main):005:0> foo = Timeout::timeout(1) do
473.    irb(main):006:1*   CACHE.get("foo")
474.    irb(main):007:1> end
475.    /usr/lib/ruby/1.8/timeout.rb:54:in `cache_get': execution expired (Timeout::Error)
476.    from /usr/lib/ruby/gems/1.8/gems/memcache-client-1.5.0/lib/memcache.rb:209:in `get'
477.    from (irb):6:in `irb_binding'
478.    from /usr/lib/ruby/1.8/timeout.rb:56:in `timeout'
479.    from (irb):5:in `irb_binding'
480.    from /usr/lib/ruby/1.8/irb/workspace.rb:52:in `irb_binding'
481.    from /usr/lib/ruby/1.8/irb/workspace.rb:52
482.    </pre>
483.    </p>
484.    <p>
485.    Do you want to guess what happened when I sent <tt>SIGCONT</tt> to memcache? My client processes, even the ones that had been hanging for hours, immediately returned with the expected data.
486.    </p>
487.    <p>
488.    The obvious thing to do is to write a new MemCache subclass decorating
489.    all the calls to <tt>get</tt>, <tt>put</tt>, <tt>get_multi</tt>, etc
490.    with safer versions. Don't naively trust that the expected data made
491.    it to the cache.
492.    </p>
493. </content>
494.   <author>
495.     <name>Steve Jenson</name>
496.     <uri>http://saladwithsteve.com/about.html</uri>
497.   </author>
498. </entry>
500. <entry>
501.   <title>More on Twitter!</title>
502.   <link href="http://saladwithsteve.com/2008/05/more-on-twitter.html"/>
503.   <updated>2008-05-22T00:00:00+00:00</updated>
504.   <id>http://saladwithsteve.com/2008/05/more-on-twitter.html</id>
505.   <content type="html">Al3x wrote up a nice blog post &lt;a href=&quot;http://dev.twitter.com/2008/05/twittering-about-architecture.html&quot;&gt;talking about the future of twitter.&lt;/a&gt;
506. </content>
507.   <author>
508.     <name>Steve Jenson</name>
509.     <uri>http://saladwithsteve.com/about.html</uri>
510.   </author>
511. </entry>
513. <entry>
514.   <title>How work is going?</title>
515.   <link href="http://saladwithsteve.com/2008/05/how-works-going.html"/>
516.   <updated>2008-05-22T00:00:00+00:00</updated>
517.   <id>http://saladwithsteve.com/2008/05/how-works-going.html</id>
518.   <content type="html">&lt;p&gt;
519.    Since I started working at Twitter last month, I put up a standard work disclaimer along the side. It <strong>always</strong> applies.
520.    </p>
521.    <p>
522.    Jack posted on the company blog: <a href="http://blog.twitter.com/2008/05/i-have-this-graph-up-on-my-screen-all.html">I have this graph up on my screen all the time. It should be flat. This week has been rough.</a>
523.    </p>
524.    <p>
525.    So we have open job postings for something called a <a href="http://twitter.com/help/jobs#syseng">Systems Engineer</a>, which is what I do at Twitter. Systems Engineering means building systems where graphs like that stay flat and where downtime means it was either planned or making sure that particular problem won't happen again (if it can be avoided: typical engineering trade-offs apply).
526.    </p>
527.    <p>
528.    Our problems are really interesting, I think. Lots of users, lots of connections, lots of messages flowing through the system, lots of endpoints, and lots of details to keep straight. All of this needs to be turned into a cohesive system that's simple to reason about and to run in order for me to consider my job a success. It's a tall order but it's what I signed up to do. I've been watching Twitter for a long time (I'm user #150) so I walked into things with my eyes wide open.
529.    </p>
530.    <p>
531.    If you've been reading this blog for a while, you know that I'm more interested in engineering than hacking together a site. Thinking and then doing. Measuring and then reasoning. Making guesses and then testing them. There's a natural tension between cowboying around and Analysis Paralysis and you have to learn to walk that tightrope if you want to succeed and I think at Twitter, we work pretty hard to Do the Right Thing.
532.    </p>
533.    <p>
534.    I'm writing this quick post because we're looking for great people who are interested in engineering big systems and in helping to make Twitter the utility-class company we see ourselves as needing to be. If you think you either have the skills or can learn them, please send us your resume to jobs@twitter.com.
535.    </p>
536. </content>
537.   <author>
538.     <name>Steve Jenson</name>
539.     <uri>http://saladwithsteve.com/about.html</uri>
540.   </author>
541. </entry>
543. <entry>
544.   <title>Fun DTrace script</title>
545.   <link href="http://saladwithsteve.com/2008/05/fun-dtrace-script.html"/>
546.   <updated>2008-05-20T00:00:00+00:00</updated>
547.   <id>http://saladwithsteve.com/2008/05/fun-dtrace-script.html</id>
548.   <content type="html">&lt;pre&gt;
549.    <code>
550.    #!/usr/sbin/dtrace -s
551.  
552.    syscall:::entry
553.    /pid == $1/
554.    {
555.    @sys[probefunc, ustack()] = count();
556.    }
557.  
558.    END {
559.    trunc(@sys, 2);
560.    }
561.    </code>
562.    </pre>
563.  
564.    Tells you the 2 most often called system call/stack trace pair. Running it against firefox 3 beta while using Google Reader shows:
565.  
566.    <pre>
567.    <code>
568.    $ sudo ./syscalldist.d 240
569.    dtrace: script './syscalldist.d' matched 428 probes
570.    ^C
571.    CPU     ID                    FUNCTION:NAME
572.    1      2                             :END
573.  
574.    munmap                                            
575.    libSystem.B.dylib`munmap$UNIX2003+0xa
576.    libSystem.B.dylib`free+0x6a
577.    CoreGraphics`CGEventCreateFromDataAndSource+0xbce
578.    CoreGraphics`CGSDecodeEventRecord+0x6a
579.    CoreGraphics`CGSDispatchDatagramsFromStream+0x28f
580.    CoreGraphics`snarfEvents+0x12a
581.    CoreGraphics`CGSGetNextEventRecordInternal+0x9f
582.    CoreGraphics`CGEventCreateNextEvent+0x2c
583.    HIToolbox`PullEventsFromWindowServerOnConnection(unsigned int, unsigned char)+0x58
584.    CoreFoundation`__CFMachPortPerform+0x75
585.    CoreFoundation`CFRunLoopRunSpecific+0xf51
586.    CoreFoundation`CFRunLoopRunInMode+0x58
587.    HIToolbox`RunCurrentEventLoopInMode+0x11b
588.    HIToolbox`ReceiveNextEventCommon+0x176
589.    HIToolbox`BlockUntilNextEventMatchingListInMode+0x6a
590.    AppKit`_DPSNextEvent+0x291
591.    AppKit`-[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:]+0x80
592.    AppKit`-[NSApplication run]+0x31b
593.    XUL`JSD_GetValueForObject+0xad6ce
594.    XUL`XRE_GetFileFromPath+0x61c563
595.    961
596.    mmap                                              
597.    libSystem.B.dylib`mmap+0xa
598.    libSystem.B.dylib`large_and_huge_malloc+0xcb
599.    libSystem.B.dylib`szone_malloc+0x1cf
600.    libSystem.B.dylib`malloc_zone_malloc+0x51
601.    libSystem.B.dylib`malloc+0x37
602.    CoreGraphics`CGEventCreateFromDataAndSource+0x15e
603.    CoreGraphics`CGSDecodeEventRecord+0x6a
604.    CoreGraphics`CGSDispatchDatagramsFromStream+0x28f
605.    CoreGraphics`snarfEvents+0x12a
606.    CoreGraphics`CGSGetNextEventRecordInternal+0x9f
607.    CoreGraphics`CGEventCreateNextEvent+0x2c
608.    HIToolbox`PullEventsFromWindowServerOnConnection(unsigned int, unsigned char)+0x58
609.    CoreFoundation`__CFMachPortPerform+0x75
610.    CoreFoundation`CFRunLoopRunSpecific+0xf51
611.    CoreFoundation`CFRunLoopRunInMode+0x58
612.    HIToolbox`RunCurrentEventLoopInMode+0x11b
613.    HIToolbox`ReceiveNextEventCommon+0x176
614.    HIToolbox`BlockUntilNextEventMatchingListInMode+0x6a
615.    AppKit`_DPSNextEvent+0x291
616.    AppKit`-[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:]+0x80
617.    997
618.    </pre>
619.    </code>
620.    Thrilling, I know!
621. </content>
622.   <author>
623.     <name>Steve Jenson</name>
624.     <uri>http://saladwithsteve.com/about.html</uri>
625.   </author>
626. </entry>
628. <entry>
629.   <title>DTrace for Java 6 on Leopard</title>
630.   <link href="http://saladwithsteve.com/2008/05/dtrace-for-java-6-on-leopard.html"/>
631.   <updated>2008-05-19T00:00:00+00:00</updated>
632.   <id>http://saladwithsteve.com/2008/05/dtrace-for-java-6-on-leopard.html</id>
633.   <content type="html">&lt;p&gt;
634.    When Java 6 for Leopard was released a few weeks ago, one thing that nobody seemed to notice was that Java now had DTrace probes on par with Java on Solaris.
635.    </p>
636.    <p>
637.    What you expect is there:
638.    <ul>
639.    <li><a href="http://www.solarisinternals.com/wiki/index.php/DTrace_Topics_Java">DTrace Topics: Java</a></li>
640.    <li><a href="http://java.sun.com/javase/6/docs/technotes/guides/vm/dtrace.html">DTrace Probes in HotSpot VM</a></li>
641.    </ul>
642.    </p>
643.    <p>
644.    With one exception: <code>jstack</code> doesn't appear to work. <code>ustack</code> works fine.
645.    </p>
646.  
647.    <p>
648.    <pre>
649.    <code>
650.    $ sudo dtrace -x jstackstrsize=2048 -n 'syscall::read:entry /execname == "java"/ { jstack(); }'
651.  
652.    dtrace: description 'syscall::read:entry ' matched 1 probe
653.    CPU     ID                    FUNCTION:NAME
654.    3  17600                       read:entry
655.  
656.    2  17600                       read:entry
657.  
658.    3  17600                       read:entry
659.  
660.    3  17600                       read:entry
661.  
662.    2  17600                       read:entry
663.  
664.    2  17600                       read:entry
665.  
666.    2  17600                       read:entry
667.  
668.    2  17600                       read:entry
669.    </code>
670.    </pre>
671.    </p>
672.  
673.    <p>
674.    There should be java stack traces under each read:entry line. (This is true even with <code>-XX:+ExtendedDTraceProbes</code> enabled)
675.    </p>
676.  
677.    <p>
678.    I used robey's scarling for my guinea pig and had a lot of fun poking around at it with dtrace.
679.    </p>
680. </content>
681.   <author>
682.     <name>Steve Jenson</name>
683.     <uri>http://saladwithsteve.com/about.html</uri>
684.   </author>
685. </entry>
687. <entry>
688.   <title>John McCarthy has a good sense of humor</title>
689.   <link href="http://saladwithsteve.com/2008/05/john-mccarthy-has-good-sense-of-humor.html"/>
690.   <updated>2008-05-11T00:00:00+00:00</updated>
691.   <id>http://saladwithsteve.com/2008/05/john-mccarthy-has-good-sense-of-humor.html</id>
692.   <content type="html">From an informal talk he gave at Stanford recently that was written up in &lt;a href=&quot;http://news.ycombinator.com/item?id=185348&quot;&gt;Hacker News&lt;/a&gt;:
693.  
694.    <blockquote>
695.    <pre>
696.    Q. Can computers know?
697.  
698.    A. This is largely a question of definition. If a camera looked at a table, we could
699.    say it "knows" that there are four containers of liquid on the table (which was true).
700.  
701.    Q. Is there any definition of "know" in which computers cannot succeed?
702.  
703.    A. Well, I suppose the biblical sense.
704.  
705.    Q. Ha, well, what makes you think that?
706.  
707.    A. They don't satisfy the necessary axioms (laughter)
708.    </pre>
709.    </blockquote>
710. </content>
711.   <author>
712.     <name>Steve Jenson</name>
713.     <uri>http://saladwithsteve.com/about.html</uri>
714.   </author>
715. </entry>
717. <entry>
718.   <title>What are you doing?</title>
719.   <link href="http://saladwithsteve.com/2008/04/what-are-you-doing.html"/>
720.   <updated>2008-04-22T00:00:00+00:00</updated>
721.   <id>http://saladwithsteve.com/2008/04/what-are-you-doing.html</id>
722.   <content type="html">reading @&lt;a href=&quot;http://blog.twitter.com/2008/04/welcome-john-and-steve.html&quot;&gt;biz&lt;/a&gt; out me as a Twitter employee.
723. </content>
724.   <author>
725.     <name>Steve Jenson</name>
726.     <uri>http://saladwithsteve.com/about.html</uri>
727.   </author>
728. </entry>
730. <entry>
731.   <title>curious what delicious is saying about something?</title>
732.   <link href="http://saladwithsteve.com/2008/04/curious-what-delicious-is-saying-about.html"/>
733.   <updated>2008-04-15T00:00:00+00:00</updated>
734.   <id>http://saladwithsteve.com/2008/04/curious-what-delicious-is-saying-about.html</id>
735.   <content type="html">&lt;a href=&quot;javascript:location.href='http://del.icio.us/url/check?&amp;url='+encodeURIComponent(location.href)&quot;&gt;Here's a bookmarklet that checks the current URL you're visiting with del.icio.us&lt;/a&gt;.
736. </content>
737.   <author>
738.     <name>Steve Jenson</name>
739.     <uri>http://saladwithsteve.com/about.html</uri>
740.   </author>
741. </entry>
743. <entry>
744.   <title>My first Thrift app</title>
745.   <link href="http://saladwithsteve.com/2008/04/my-first-thrift-app.html"/>
746.   <updated>2008-04-13T00:00:00+00:00</updated>
747.   <id>http://saladwithsteve.com/2008/04/my-first-thrift-app.html</id>
748.   <content type="html">&lt;p&gt;
749.    When you find yourself working on big systems, a useful technique is
750.    to decompose it into services. Moving from a big monolithic server to
751.    a bunch of separate services can be a big challenge but if you had
752.    foresight, many of your services were already decoupled in your system
753.    from day 1 even though you were deploying it monolithicly.
754.    </p>
755.    <p>
756.    A common technique for decomposing services is using RPC. At Google, we
757.    used protocol buffers, which were briefly descibed in the <a href="http://labs.google.com/papers/sawzall-sciprog.pdf">Sawzall</a>
758.    paper.
759.    </p>
760.    <p>
761.    Basically, you describe your data and the interface that process the
762.    data in a language-independent format (a DDL, essentially) and use code
763.    generators to turn that DDL into set of objects in your target
764.    langauge that can create and send those structures over the wire. This
765.    makes it easy to write servers in one language and clients in another
766.    and the generated code deals with serialization.
767.    </p>
768.    <p>
769.    I found that using a DDL to describe your code and services was really
770.    nice. When building a new service, you could simply reference your DDL
771.    in the design doc and have a meanginful discussion about the service
772.    without getting into the details of how it would be written until you had
773.    the semantics nailed down.
774.    </p>
775.  
776.    <p>
777.    Facebook, as they were growing, decided to move to a homegrown binary
778.    RPC mechanism similar to protocol buffers called <a href="http://developers.facebook.com/thrift/">Thrift</a>.
779.    </p>
780.  
781.    <p>
782.    Let's say I wanted to write a simple service that would tell the
783.    client what time it was on the server. Here would be the DDL file
784.    describing both the data and the service plus a little extra to help
785.    out the generated code files.
786.    </p>
787.    <pre name="code" class="thrift">
788.    # time.thrift
789.    namespace java tserver.gen
790.    namespace ruby TServer.Gen
791.  
792.    typedef i64 Timestamp
793.  
794.    service TimeServer {
795.    // Simply returns the current time.
796.    Timestamp time()
797.    }
798.    </pre>
799.  
800.    <p>
801.    After running <tt>thrift --gen java --gen rb time.thrift</tt> on the
802.    file, I'd have an interface and server that I could implement in Java
803.    and a client that I could use in Ruby.
804.    </p>
805.    <p>
806.    Based on the generated java code, I could write a short server in Scala:
807.    </p>
808.  
809.    <pre name="code" class="scala">
810.    <code>
811.    package tserver
812.  
813.    import tserver.gen._
814.    import com.facebook.thrift.TException
815.    import com.facebook.thrift.TProcessor
816.    import com.facebook.thrift.TProcessorFactory
817.    import com.facebook.thrift.protocol.TProtocol
818.    import com.facebook.thrift.protocol.TProtocolFactory
819.    import com.facebook.thrift.transport.TServerTransport
820.    import com.facebook.thrift.transport.TServerSocket
821.    import com.facebook.thrift.transport.TTransport
822.    import com.facebook.thrift.transport.TTransportFactory
823.    import com.facebook.thrift.transport.TTransportException
824.    import com.facebook.thrift.server.TServer
825.    import com.facebook.thrift.server.TThreadPoolServer
826.    import com.facebook.thrift.protocol.TBinaryProtocol
827.  
828.    /**
829.    * TimeServer.time returns the current time according to the server.
830.    */
831.    class TimeServer extends TimeServer.Iface {
832.    override def time: Long = {
833.    val now = System.currentTimeMillis
834.    println("somebody just asked me what time it is: " + now)
835.    now
836.    }
837.    }
838.  
839.    object SimpleServer extends Application {
840.    try {
841.    val serverTransport = new TServerSocket(7911)
842.    val processor = new TimeServer.Processor(new TimeServer())
843.    val protFactory = new TBinaryProtocol.Factory(true, true)
844.    val server = new TThreadPoolServer(processor, serverTransport,
845.    protFactory)
846.    
847.    println("starting server")
848.    server.serve();    
849.    } catch {
850.    case x: Exception => x.printStackTrace();
851.    }
852.    }
853.    </code>
854.    </pre>
855.  
856.    <p>
857.    (Geez, most of that space was taken up in my obsessive need to separate
858.    out all my imports. You can thank Google for that bit of OCD.)
859.    </p>
860.    <p>
861.    The client is even shorter:
862.    </p>
863.    <pre name="code" class="ruby">
864.    <code>
865.    #!/usr/bin/ruby
866.    $:.push('~/thrift/lib/rb/lib')
867.    $:.push('../gen-rb')
868.  
869.    require 'thrift/transport/tsocket'
870.    require 'thrift/protocol/tbinaryprotocol'
871.    require 'TimeServer'
872.  
873.    transport = TBufferedTransport.new(TSocket.new("localhost", 7911))
874.    protocol = TBinaryProtocol.new(transport)
875.    client = TimeServer::Client.new(protocol)
876.  
877.    transport.open()
878.  
879.    puts "I wonder what time it is. Let's ask!"
880.    puts client.time()
881.    </code>
882.    </pre>
883.    <p>
884.    The ruby client took about 20ms to get an answer from the Scala server.
885.    </p>
886.    <p>
887.    Thrift advantages:<br />
888.    <ul>
889.    <li>Pipelined connections means you spend less time in connection setup/teardown and TCP likes longer-lived connections.</li>
890.    <li>Asynchronous requests. Asynchronous replies would be nice too but would be trickier to use.</li>
891.    <li>Binary representation is much more efficient to transmit and process than, say, XML.</li>
892.    </ul>
893.    </p>
894.    <p>
895.    Thrift drawbacks: <br />
896.    <ul>
897.    <li>Integrating generated source into your build system can be tricky.
898.    Typically, you rarely have to regenerate your stubs but debugging generated code can be a huge pain.</li>
899.    <li>It's Java server should move away from ServerSocket to NIO for increased throughput.
900.    That's probably not more than a week's work as long as the existing code isn't too tightly coupled.</li>
901.    <li>Currently it doesn't build cleanly on the Mac. I did some work and got it working but I don't think it's used
902.    extensively on the Mac so if that's your primary platform, you should be prepared to send them patches from time to time.</li>
903.    </ul>
904.    </p>
905.    <p>
906.    If you're looking to move towards decoupled services, Thrift is worth a hard look.
907.    </p>
908.    <p>
909.    Here's a tarball with my <a href="http://saladwithsteve.com//code/timeserver.tar.gz">time
910.    server</a>. It contains all the generated code as well as
911.    libthrift.jar and a Makefile to run the example server.
912.    </p>
913. </content>
914.   <author>
915.     <name>Steve Jenson</name>
916.     <uri>http://saladwithsteve.com/about.html</uri>
917.   </author>
918. </entry>
920. <entry>
921.   <title>GVN and gold</title>
922.   <link href="http://saladwithsteve.com/2008/04/gvn-and-gold.html"/>
923.   <updated>2008-04-07T00:00:00+00:00</updated>
924.   <id>http://saladwithsteve.com/2008/04/gvn-and-gold.html</id>
925.   <content type="html">&lt;p&gt;
926.    Two things popped up on my radar recently:
927.    </p>
928.    <p>
929.    <a href="http://code.google.com/p/gvn/">gvn</a>, Google's wrappers around Subversion to help them work in their code-review heavy workflow. Even if you're not into code reviews, <code>tkdiff</code> integration is a nice improvement over <code>colordiff</code> or <code>FileMerge</code>.
930.    </p>
931.    <p>
932.    <a href="http://www.airs.com/blog/archives/164">gold</a>, a new ELF linker built with giant binaries in mind. When you're building 900MB+ static binaries routinely, linking speed matters. gold claims to be at least 5x faster currently. Even if you have a massive distcc cluster, linking is still serial. One of gold's future design goals is to be concurrent and that would be pretty awesome. Imagine how fast I could link with a concurrent linker on my 8-core Mac Pro! Not that using an ELF linker under Leopard helps much since OS X uses Mach-O binaries but hey, there's always cross-compiling.
933.    </p>
934.    <p>
935.    BTW, Ian Lance Taylor, the author of gold, has <a href="http://www.airs.com/blog/archives/38">an excellent series of blog articles on linkers.</a>
936.    </p>
937. </content>
938.   <author>
939.     <name>Steve Jenson</name>
940.     <uri>http://saladwithsteve.com/about.html</uri>
941.   </author>
942. </entry>
944. </feed>
945.  

If you would like to create a banner that links to this page (i.e. this validation result), do the following:

1. Download the "valid Atom 1.0" banner.

2. Upload the image to your own server. (This step is important. Please do not link directly to the image on this server.)

3. Add this HTML to your page (change the image src attribute if necessary):

   <a href="http://www.feedvalidator.org/check.cgi?url=http%3A//saladwithsteve.com/atom.xml"><img src="valid-atom.png" alt="[Valid Atom 1.0]" title="Validate my Atom 1.0 feed" /></a>

If you would like to create a text link instead, here is the URL you can use:

http://www.feedvalidator.org/check.cgi?url=http%3A//saladwithsteve.com/atom.xml

Home · About · News · Docs · Terms