<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments for A Wicket Diary</title>
	<atom:link href="http://martijndashorst.com/blog/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://martijndashorst.com/blog</link>
	<description>Ramblings on Java, Wicket, cats and other stuff</description>
	<lastBuildDate>Mon, 05 Dec 2011 20:15:59 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>Comment on EHCache and Quartz phone home during startup by Mark Wood</title>
		<link>http://martijndashorst.com/blog/2011/02/21/ehcache-and-quartz-phone-home-during-startup/comment-page-1/#comment-61384</link>
		<dc:creator>Mark Wood</dc:creator>
		<pubDate>Mon, 05 Dec 2011 20:15:59 +0000</pubDate>
		<guid isPermaLink="false">http://martijndashorst.com/blog/?p=482#comment-61384</guid>
		<description>o  One might not even know one is *using* EHCache or Quartz or xxx until one sees these log messages.  They could be buried several layers deep in dependencies.  How to know that one can/should turn something off, when one doesn&#039;t even know it&#039;s there to *be* turned off?

o  Opt-in is a community norm.  You&#039;re supposed to expect people to be suspicious.  You&#039;re supposed to leave things like phone-home off by default.  You&#039;re supposed to explain what it does for the user and trust him to have some sympathy with the goals of people who give away useful stuff.  This is probably why people get angry.

o  Big applications take long enough to start.  If various bits are phoning home when they initialize, people will feel that the overhead of DNS resolution and TCP handshake (not to mention whatever the application layer is doing) add too much startup cost, whether it&#039;s true or not.  And, while big app.s may run for a long time, they may *also* have little commandline pieces that are run very frequently but which pay the same overhead because they use the same core code (reusability, you know).</description>
		<content:encoded><![CDATA[<p>o  One might not even know one is *using* EHCache or Quartz or xxx until one sees these log messages.  They could be buried several layers deep in dependencies.  How to know that one can/should turn something off, when one doesn&#8217;t even know it&#8217;s there to *be* turned off?</p>
<p>o  Opt-in is a community norm.  You&#8217;re supposed to expect people to be suspicious.  You&#8217;re supposed to leave things like phone-home off by default.  You&#8217;re supposed to explain what it does for the user and trust him to have some sympathy with the goals of people who give away useful stuff.  This is probably why people get angry.</p>
<p>o  Big applications take long enough to start.  If various bits are phoning home when they initialize, people will feel that the overhead of DNS resolution and TCP handshake (not to mention whatever the application layer is doing) add too much startup cost, whether it&#8217;s true or not.  And, while big app.s may run for a long time, they may *also* have little commandline pieces that are run very frequently but which pay the same overhead because they use the same core code (reusability, you know).</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Connecting to MongoLabs on heroku by James Ward</title>
		<link>http://martijndashorst.com/blog/2011/11/24/connecting-to-mongolabs-on-heroku/comment-page-1/#comment-61339</link>
		<dc:creator>James Ward</dc:creator>
		<pubDate>Mon, 28 Nov 2011 01:16:14 +0000</pubDate>
		<guid isPermaLink="false">http://martijndashorst.com/blog/?p=501#comment-61339</guid>
		<description>This isn&#039;t well documented at the moment.  Sorry.  It&#039;s something we are working on.  Check out a Java example here:
https://github.com/jamesward/jetty-mongo-session-test/blob/master/src/main/java/com/heroku/test/Main.java

-James</description>
		<content:encoded><![CDATA[<p>This isn&#8217;t well documented at the moment.  Sorry.  It&#8217;s something we are working on.  Check out a Java example here:<br />
<a href="https://github.com/jamesward/jetty-mongo-session-test/blob/master/src/main/java/com/heroku/test/Main.java" rel="nofollow">https://github.com/jamesward/jetty-mongo-session-test/blob/master/src/main/java/com/heroku/test/Main.java</a></p>
<p>-James</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Introducing Apache Wicket by Nick Heudecker by Hans-Heinrich Braun</title>
		<link>http://martijndashorst.com/blog/2008/01/28/introducing-apache-wicket-by-nick-heudecker/comment-page-1/#comment-61201</link>
		<dc:creator>Hans-Heinrich Braun</dc:creator>
		<pubDate>Sun, 16 Oct 2011 11:21:18 +0000</pubDate>
		<guid isPermaLink="false">http://martijndashorst.com/blog/2008/01/28/introducing-apache-wicket-by-nick-heudecker/#comment-61201</guid>
		<description>I followed for a long time the Apache Cocoon project.
Developing Forms became a nightmare with Flowscript and all the Transformers an Generators.
Cocoon 3 started the cooperation with Wicket.
Frustrated by the integration of Dojo I examined Wicket and I was surprised how easy 
Form development could be and how adaptable it is.
After 2 weeks of experience I read your article, and found my way would have been less sony when I had encountered it at the beginning.</description>
		<content:encoded><![CDATA[<p>I followed for a long time the Apache Cocoon project.<br />
Developing Forms became a nightmare with Flowscript and all the Transformers an Generators.<br />
Cocoon 3 started the cooperation with Wicket.<br />
Frustrated by the integration of Dojo I examined Wicket and I was surprised how easy<br />
Form development could be and how adaptable it is.<br />
After 2 weeks of experience I read your article, and found my way would have been less sony when I had encountered it at the beginning.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The sorry state of subversion support in Eclipse by Radu</title>
		<link>http://martijndashorst.com/blog/2009/05/05/the-sorry-state-of-subversion-support-in-eclipse/comment-page-1/#comment-61180</link>
		<dc:creator>Radu</dc:creator>
		<pubDate>Tue, 11 Oct 2011 08:48:03 +0000</pubDate>
		<guid isPermaLink="false">http://martijndashorst.com/blog/2009/05/05/the-sorry-state-of-subversion-support-in-eclipse/#comment-61180</guid>
		<description>Nice page for ranting about Eclipse IDE shortcomings. So here goes:
On a past project I had to use CVS from Eclipse.
But i REALLY want to use Subversion. And no, I do not need or have time to learn GIT, or to use other complex tools like Perforce.
I just want SVN to work with Eclipse. 
Also, the updates are horrible on Eclipse, I agree with the opinions above. I just delete and reinstall new builds every months...
Is it so damn hard?</description>
		<content:encoded><![CDATA[<p>Nice page for ranting about Eclipse IDE shortcomings. So here goes:<br />
On a past project I had to use CVS from Eclipse.<br />
But i REALLY want to use Subversion. And no, I do not need or have time to learn GIT, or to use other complex tools like Perforce.<br />
I just want SVN to work with Eclipse.<br />
Also, the updates are horrible on Eclipse, I agree with the opinions above. I just delete and reinstall new builds every months&#8230;<br />
Is it so damn hard?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on EHCache and Quartz phone home during startup by Erik van Oosten</title>
		<link>http://martijndashorst.com/blog/2011/02/21/ehcache-and-quartz-phone-home-during-startup/comment-page-1/#comment-61176</link>
		<dc:creator>Erik van Oosten</dc:creator>
		<pubDate>Mon, 10 Oct 2011 10:48:46 +0000</pubDate>
		<guid isPermaLink="false">http://martijndashorst.com/blog/?p=482#comment-61176</guid>
		<description>The XML fragment should have been:

    &lt;properties&gt;
         &lt;property name=&quot;hazelcast.version.check.enabled&quot;&gt;false&lt;/property&gt;
    &lt;/properties&gt;</description>
		<content:encoded><![CDATA[<p>The XML fragment should have been:</p>
<p>    &lt;properties&gt;<br />
         &lt;property name=&#8221;hazelcast.version.check.enabled&#8221;&gt;false&lt;/property&gt;<br />
    &lt;/properties&gt;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

