<?xml version="1.0" encoding="ISO-8859-1"?><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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments for out of the way</title>
	<atom:link href="http://gfrison.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://gfrison.com</link>
	<description>Fundamentals never go out of style</description>
	<lastBuildDate>Thu, 30 Apr 2009 07:05:44 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Powered by Apache Mina by Nyarlathotep</title>
		<link>http://gfrison.com/2009/04/24/powered-by-apache-mina/#comment-63</link>
		<dc:creator>Nyarlathotep</dc:creator>
		<pubDate>Thu, 30 Apr 2009 07:05:44 +0000</pubDate>
		<guid isPermaLink="false">http://gfrison.com/?p=73#comment-63</guid>
		<description>Mina isn&#039;t limited to request-response only.
Everytime some bytes commining in, or you are writing a message to the session, a chain of filters is triggered. You can specify the filters on your needs. One of them is the (Demuxing)ProtocolCodecFilter which takes a decoder and an encoder.
You just call IoSession.write() with you message object and the encoder will be triggered.
When bytes dripping in, the decoder will be triggered and, if finished, the parsed message object forwarded to the next filter.
Your app won&#039;t get in contact with the byte stream, which offers a nice abstraction of the underlying protocol.</description>
		<content:encoded><![CDATA[<p>Mina isn&#8217;t limited to request-response only.<br />
Everytime some bytes commining in, or you are writing a message to the session, a chain of filters is triggered. You can specify the filters on your needs. One of them is the (Demuxing)ProtocolCodecFilter which takes a decoder and an encoder.<br />
You just call IoSession.write() with you message object and the encoder will be triggered.<br />
When bytes dripping in, the decoder will be triggered and, if finished, the parsed message object forwarded to the next filter.<br />
Your app won&#8217;t get in contact with the byte stream, which offers a nice abstraction of the underlying protocol.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Powered by Apache Mina by Giancarlo Frison</title>
		<link>http://gfrison.com/2009/04/24/powered-by-apache-mina/#comment-61</link>
		<dc:creator>Giancarlo Frison</dc:creator>
		<pubDate>Wed, 29 Apr 2009 19:14:00 +0000</pubDate>
		<guid isPermaLink="false">http://gfrison.com/?p=73#comment-61</guid>
		<description>Sure. Once you get the IoSession, from TCP connection for instance, you could forward packets in whatever thread you need using IoSession.write().</description>
		<content:encoded><![CDATA[<p>Sure. Once you get the IoSession, from TCP connection for instance, you could forward packets in whatever thread you need using IoSession.write().</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Powered by Apache Mina by kwade</title>
		<link>http://gfrison.com/2009/04/24/powered-by-apache-mina/#comment-60</link>
		<dc:creator>kwade</dc:creator>
		<pubDate>Wed, 29 Apr 2009 17:09:44 +0000</pubDate>
		<guid isPermaLink="false">http://gfrison.com/?p=73#comment-60</guid>
		<description>Very interesting.  Especially the part about DemuxingIoHandler; very cool.  But, I am curious as to how one would use mina to &quot;forward notifications asynchronously to the client.&quot;  I can see how mina allows for a request/response type of handling.  But it&#039;s not obvious to me how -- if you had some server-side event happen that you wanted to notify clients about -- you could get connections to those connected clients and then push a message to them asynchronously?</description>
		<content:encoded><![CDATA[<p>Very interesting.  Especially the part about DemuxingIoHandler; very cool.  But, I am curious as to how one would use mina to &#8220;forward notifications asynchronously to the client.&#8221;  I can see how mina allows for a request/response type of handling.  But it&#8217;s not obvious to me how &#8212; if you had some server-side event happen that you wanted to notify clients about &#8212; you could get connections to those connected clients and then push a message to them asynchronously?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Powered by Apache Mina by Ashish</title>
		<link>http://gfrison.com/2009/04/24/powered-by-apache-mina/#comment-59</link>
		<dc:creator>Ashish</dc:creator>
		<pubDate>Tue, 28 Apr 2009 03:56:29 +0000</pubDate>
		<guid isPermaLink="false">http://gfrison.com/?p=73#comment-59</guid>
		<description>Great article!</description>
		<content:encoded><![CDATA[<p>Great article!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Recruiter advisory: Explicit lyrics by John Moore</title>
		<link>http://gfrison.com/2009/03/13/recruiter-advisory-explicit-lyrics/#comment-54</link>
		<dc:creator>John Moore</dc:creator>
		<pubDate>Fri, 10 Apr 2009 02:24:48 +0000</pubDate>
		<guid isPermaLink="false">http://gfrison.com/?p=41#comment-54</guid>
		<description>Good tips throughout.  The key for me, as a hiring manager, is often the behavioral portion of the interview.  Trying to get inside of a candidate&#039;s head to more thoroughly understand what makes them tick is the hardest, but potentially the most rewarding, skill to gain.

If you have a chance, check out my blog posting on how startups should go about choosing a recruiting partner.  Based upon the advice here to recruiter&#039;s I feel the readers of my blog might get some good insights from any comments you could provide.

http://johnfmoore.wordpress.com/2009/03/18/find-the-right-recruiting-partner-for-your-startup/

John
http://johnfmoore.wordpress.com</description>
		<content:encoded><![CDATA[<p>Good tips throughout.  The key for me, as a hiring manager, is often the behavioral portion of the interview.  Trying to get inside of a candidate&#8217;s head to more thoroughly understand what makes them tick is the hardest, but potentially the most rewarding, skill to gain.</p>
<p>If you have a chance, check out my blog posting on how startups should go about choosing a recruiting partner.  Based upon the advice here to recruiter&#8217;s I feel the readers of my blog might get some good insights from any comments you could provide.</p>
<p><a href="http://johnfmoore.wordpress.com/2009/03/18/find-the-right-recruiting-partner-for-your-startup/" rel="nofollow">http://johnfmoore.wordpress.com/2009/03/18/find-the-right-recruiting-partner-for-your-startup/</a></p>
<p>John<br />
<a href="http://johnfmoore.wordpress.com" rel="nofollow">http://johnfmoore.wordpress.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Chain of failures on blocking threads by Giancarlo Frison</title>
		<link>http://gfrison.com/2008/06/11/chain-of-failures-on-blocking-threads/#comment-10</link>
		<dc:creator>Giancarlo Frison</dc:creator>
		<pubDate>Thu, 19 Jun 2008 07:40:11 +0000</pubDate>
		<guid isPermaLink="false">http://giancarlof.wordpress.com/?p=14#comment-10</guid>
		<description>Thank you Chatchai. 
The point isn&#039;t the task&#039;s failure but its delay. 
I want to put in a timebox every task that may delay or block an whole process flow execution. 
Maybe during the login we encounter tcp latency that shifts our task, or the endpoint disappear without any warning, hunging our request. It would trigger unpredictable failures drugging the hung to other components.</description>
		<content:encoded><![CDATA[<p>Thank you Chatchai.<br />
The point isn&#8217;t the task&#8217;s failure but its delay.<br />
I want to put in a timebox every task that may delay or block an whole process flow execution.<br />
Maybe during the login we encounter tcp latency that shifts our task, or the endpoint disappear without any warning, hunging our request. It would trigger unpredictable failures drugging the hung to other components.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Chain of failures on blocking threads by Chatchai</title>
		<link>http://gfrison.com/2008/06/11/chain-of-failures-on-blocking-threads/#comment-9</link>
		<dc:creator>Chatchai</dc:creator>
		<pubDate>Thu, 19 Jun 2008 03:29:40 +0000</pubDate>
		<guid isPermaLink="false">http://giancarlof.wordpress.com/?p=14#comment-9</guid>
		<description>Good Post.

Just one minor thing I&#039;d like to add. ExecutorService know nothing about the timeout. TimeoutException has been thrown just to tell us that the get(timeout,timeunit) was timeout. It  didn&#039;t mean that the execution was failed. If the task take around 8 secs and you call get(3 secs) in a loop then you may get TimeoutException for the first and second call and get the result on the third.</description>
		<content:encoded><![CDATA[<p>Good Post.</p>
<p>Just one minor thing I&#8217;d like to add. ExecutorService know nothing about the timeout. TimeoutException has been thrown just to tell us that the get(timeout,timeunit) was timeout. It  didn&#8217;t mean that the execution was failed. If the task take around 8 secs and you call get(3 secs) in a loop then you may get TimeoutException for the first and second call and get the result on the third.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
