<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Disqus - Latest Comments for cawel</title><link>http://disqus.com/by/cawel/</link><description></description><atom:link href="http://disqus.com/cawel/comments.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Fri, 08 Mar 2013 11:19:00 -0000</lastBuildDate><item><title>Re: Removing config.threadsafe! |  Tenderlovemaking</title><link>http://tenderlovemaking.com/2012/06/18/removing-config-threadsafe.html#comment-823056557</link><description>&lt;p&gt;That was a useful and practical article, thank you! Unfortunately, I found some parts to be ambiguous. Here are 3 examples.&lt;/p&gt;&lt;p&gt;In your conclusion, you say that it is "absolutely necessary [to enable config.threadsafe!] in a multi-threaded environment". But you have an example in your blog post where you disabled "config.threadsafe!" in a multi-threaded environment, and it worked just fine (i.e. with no side effects, in a context where performance is not an issue). "Crippling" your multi-threaded server with the @allow_concurrency flag might just be desired for some reason.&lt;/p&gt;&lt;p&gt;Also, in the very last paragraph, when you say "this flag", it took me quite a while to understand that you meant the "@allow_concurrency" flag, and not "config.threadsafe!".&lt;/p&gt;&lt;p&gt;And finally, because of a confusing method naming, I think you should be explicit (probably early in your article) about the intention of "config.threasafe!": you are telling the framework that your *own* app code is thread-safe (as opposed to telling the framework to enable some thread-safe feature, because your own app code is not thread-safe).&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Martin Carel</dc:creator><pubDate>Fri, 08 Mar 2013 11:19:00 -0000</pubDate></item><item><title>Re: GiraffeSoft | Welcome to smarter web app development.</title><link>http://giraffesoft.ca/blog/2009/02/26/how-to-use-timelinefu-building-an-activity-feed-for-a-social-application.html#comment-6682123</link><description>&lt;p&gt;Nice tutorial! I will be using this for sure, so I thought I'd give you 2 comments as a mini-mini contribution to this plugin:&lt;/p&gt;&lt;p&gt;In your second RelationshipTest code snippet, you have the relationship as the subject, whereas it should be the *secondary* subject and the old friend as the subject (just like you defined it earlier in the text, and just like it is in the github repo). Same thing goes for the Relationship code snippet.&lt;/p&gt;&lt;p&gt;And second, in your PersonTest code snippet, IMHO, if you had the setup code in there, it would be more explicit as to what the @person variable is.&lt;/p&gt;&lt;p&gt;What do you say?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Martin Carel</dc:creator><pubDate>Fri, 27 Feb 2009 01:47:24 -0000</pubDate></item></channel></rss>