<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>AVH4 - Latest Comments</title><link xmlns="http://www.w3.org/2005/Atom" rel="http://api.friendfeed.com/2008/03#sup" href="http://disqus.com/sup/all.sup#forumcomments-dbe9933c" type="application/json"/><link>http://avh4.disqus.com/</link><description></description><atom:link href="http://avh4.disqus.com/comments.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Sat, 06 Jun 2009 09:08:45 -0000</lastBuildDate><item><title>Re: undefined method `register_service&amp;#8217; for Net::SSH:Module</title><link>http://www.avh4.net/wp/2008/09/03/undefined-method-register_service-for-netsshmodule/#comment-10562272</link><description>&lt;p&gt;If, after you install an older version of net-ssh, you see the following exception, then for me it was because I had the wrong port #:&lt;/p&gt;

&lt;p&gt;c:/ruby/lib/ruby/gems/1.8/gems/net-ssh-1.1.4/lib/net/ssh/transport/session.rb:95:in `initialize': Bad file descriptor - connect(2) (Errno::EBADF)&lt;br&gt;        from c:/ruby/lib/ruby/gems/1.8/gems/net-ssh-1.1.4/lib/net/ssh/transport/session.rb:95:in `open'&lt;br&gt;        from c:/ruby/lib/ruby/gems/1.8/gems/net-ssh-1.1.4/lib/net/ssh/transport/session.rb:95:in `initialize'&lt;br&gt;        from c:/ruby/lib/ruby/1.8/timeout.rb:48:in `timeout'&lt;br&gt;        from c:/ruby/lib/ruby/1.8/timeout.rb:76:in `timeout'&lt;br&gt;        from c:/ruby/lib/ruby/gems/1.8/gems/net-ssh-1.1.4/lib/net/ssh/transport/session.rb:94:in `initialize'&lt;br&gt;        from c:/ruby/lib/ruby/gems/1.8/gems/net-ssh-1.1.4/lib/net/ssh/transport/services.rb:121:in `new'&lt;br&gt;        from c:/ruby/lib/ruby/gems/1.8/gems/net-ssh-1.1.4/lib/net/ssh/transport/services.rb:121:in `register_services'&lt;br&gt;        from c:/ruby/lib/ruby/gems/1.8/gems/needle-1.3.0/lib/needle/lifecycle/singleton.rb:42:in `call'&lt;br&gt;         ... 43 levels...&lt;br&gt;        from c:/ruby/lib/ruby/gems/1.8/gems/capistrano-1.4.1/lib/capistrano/cli.rb:12:in `execute!'&lt;br&gt;        from c:/ruby/lib/ruby/gems/1.8/gems/capistrano-1.4.1/bin/cap:11&lt;br&gt;        from c:/ruby/bin/cap:18:in `load'&lt;br&gt;        from c:/ruby/bin/cap:18&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ryan Shillington</dc:creator><pubDate>Sat, 06 Jun 2009 09:08:45 -0000</pubDate></item><item><title>Re: undefined method `register_service&amp;#8217; for Net::SSH:Module</title><link>http://www.avh4.net/wp/2008/09/03/undefined-method-register_service-for-netsshmodule/#comment-2529447</link><description>&lt;p&gt;that worked perfectly, thanks!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">shanaver</dc:creator><pubDate>Mon, 22 Sep 2008 23:54:32 -0000</pubDate></item><item><title>Re: New concept for approaching Mac application development</title><link>http://www.avh4.net/wp/2008/09/03/new-concept-for-approaching-mac-application-development/#comment-2180955</link><description>&lt;p&gt;I'm not really thinking of it as giving people complexity-- instead I'm thinking of it more as completely separate applications that just happen to use the same backend data.&lt;/p&gt;

&lt;p&gt;There are quite a few classes of applications that have this type of record-list data:  Time tracking is one; address book, calendar, bank account, passwords are another.  I think this same pattern would be interesting to apply to all those different areas.  For instance, Apple provides an API to access iCal data, and there are now many applications that integrate with iCal in different ways.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Aaron V.</dc:creator><pubDate>Sat, 06 Sep 2008 03:35:00 -0000</pubDate></item><item><title>Re: New concept for approaching Mac application development</title><link>http://www.avh4.net/wp/2008/09/03/new-concept-for-approaching-mac-application-development/#comment-2152003</link><description>&lt;p&gt;Hey, while from a software engineering standpoint this is a great idea, I think this is a sledgehammer approach, really. IMHO TimeTracker is a very simple application and looking at the current feature requests it wont get the next "Office" any time soon. Therefore, I think that most users wont appreciate the added flexibility / complexity that comes with such an approach. Instead we should focus on keeping TimeTracker what it is: a small, effective and efficient tool to record your time.&lt;/p&gt;

&lt;p&gt;Just my 2 cents&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Rainer</dc:creator><pubDate>Fri, 05 Sep 2008 18:47:26 -0000</pubDate></item></channel></rss>
