From wmorgan-rubytorrent-devel at masanjin.net Fri Feb 4 13:21:06 2005 From: wmorgan-rubytorrent-devel at masanjin.net (William Morgan) Date: Fri Feb 4 13:17:59 2005 Subject: [rubytorrent-devel] Testing preRelease 0.3 In-Reply-To: <41F6D773.9060005@exceptionfault.de> References: <41F6D773.9060005@exceptionfault.de> Message-ID: <20050204182106.GA2698@masanjin.net> I've made a lot of updates in CVS and hopefully fixed the problems mentioned. I've also added a nice ncurses interface, if anyone would like to play with it. Just run rtpeer-ncurses.rb. The biggest performance issue I fixed was getting the first piece on a fresh download---when you have no pieces of your own to bargain with, you're at the mercy of everyone else, and you have to be kind of careful in how you allocate your requests. I've tweaked RubyTorrent's behavior in fuseki mode and I think this is resolved now. The freeze issue on outgoing connections, however, is definitely a Ruby-on-Windows issue. See my latest ruby-talk post for details. If no one replies to that soon, I will take it to ruby-core. Hopefully there's a solution that doesn't involve patching Ruby. Feel free to test and send me any bugs you find. -- William From wmorgan-rubytorrent-devel at masanjin.net Sun Feb 6 08:03:54 2005 From: wmorgan-rubytorrent-devel at masanjin.net (William Morgan) Date: Sun Feb 6 08:00:47 2005 Subject: [rubytorrent-devel] [usa@garbagecollect.jp: Re: windows socket connection freeze] Message-ID: <20050206130353.GA5878@masanjin.net> Here's the status of the patch for Ruby that solves the freezing issue on Windows. ----- Forwarded message from "U.Nakamura" ----- Date: Sun, 6 Feb 2005 14:58:19 +0900 From: "U.Nakamura" To: ruby-core@ruby-lang.org Subject: Re: windows socket connection freeze Hello, In message "windows socket connection freeze" on Feb.05,2005 23:04:46, wrote: | Was the issue described in [ruby-core:3154] ever resolved? I'm | experiencing the same behavior with Ruby 1.8.2 2004-12-25 | [i386-mswin32]: when I open a TCP socket to a bogus IP address, *all* | threads freeze until the TCP timeout is reached. This doesn't happen on | Linux. It's fixed at CVS HEAD. If someone reports that there is no problem, I' backport it to 1.8. Regards, -- U.Nakamura ----- End forwarded message ----- -- William From curtis.schofield at gmail.com Mon Feb 7 02:06:06 2005 From: curtis.schofield at gmail.com (Curtis Schofield) Date: Mon Feb 7 02:02:56 2005 Subject: [rubytorrent-devel] Trying to Seed Maybe Bug? Message-ID: <3470c3fd0746f43e782395abe8ec3614@gmail.com> Hi, trying to get rubytorrent to act as a seeder. I'm instantiation the RubyTorrent::Bittorrent with a pre-created MetaInfo object... bt = RubyTorrent::BitTorrent.new(dtorrent.metainfo) bt.on_event(self, :tracker_connected) { |s, url| puts "[tracker] connected to tracker #{url}" } I will attack the test file (just some random strings in a file) and the torrent that was generated for it. . -------------- next part -------------- A non-text attachment was scrubbed... Name: Porp.avi.torrent Type: application/octet-stream Size: 245 bytes Desc: not available Url : http://rubyforge.org/pipermail/rubytorrent-devel/attachments/20050207/b0b50cb8/Porp.avi.obj -------------- next part -------------- A non-text attachment was scrubbed... Name: Porp.avi Type: video/x-msvideo Size: 76 bytes Desc: not available Url : http://rubyforge.org/pipermail/rubytorrent-devel/attachments/20050207/b0b50cb8/Porp.avi -------------- next part -------------- Below is the error --- (druby://localhost:54744) ./3rdParty/rubytorrent/rubytorrent/typedstruct.rb:76:in `method_missing': no such value info (ArgumentError) from (druby://localhost:54744) ./3rdParty/rubytorrent/rubytorrent/metainfo.rb:128:in `send' from (druby://localhost:54744) ./3rdParty/rubytorrent/rubytorrent/metainfo.rb:128:in `method_missing' from (druby://localhost:54744) ./3rdParty/rubytorrent/rubytorrent/package.rb:488:in `initialize' from (druby://localhost:54744) ./3rdParty/rubytorrent/rubytorrent.rb:54:in `new' from (druby://localhost:54744) ./3rdParty/rubytorrent/rubytorrent.rb:54:in `initialize' Below is a Dump of the object that i passed -- # {"name"=>"Porp.avi", "pieces"=>"r7p\311\030\362\335\030z\212\302\0260\031\035b\311b-`", "piece length"=>65536, "length"=>76}, "creation date"=>1107759320, "created by"=> "RubyTorrent make-metainfo (http://rubytorrent.rubyforge.org)", "comment"=>"Blah!", "announce"=>"http://localhost:6969"}, @s= #true, :creation_date=>false, :info=>false, :comment=>false, :announce=>false, :created_by=>false, :encoding=>false}, @coerce= {:announce_list=> #, :creation_date=> #, :info=> #, :announce=> #}, @dirty=true, @field= {:announce_list=>Array, :creation_date=>Time, :info=>RubyTorrent::MetaInfoInfo, :comment=>String, :announce=>URI::HTTP, :created_by=>String, :encoding=>String}, @label= {:announce_list=>"announce-list", :creation_date=>"creation date", :info=>"info", :comment=>"comment", :announce=>"announce", :created_by=>"created by", :encoding=>"encoding"}, @required= {:announce_list=>false, :creation_date=>false, :info=>false, :comment=>false, :announce=>false, :created_by=>false, :encoding=>false}, @values= {:creation_date=>Sun Feb 06 23:55:20 MST 2005, :info=> #"Porp.avi", "pieces"=>"r7p\311\030\362\335\030z\212\302\0260\031\035b\311b-`", "piece length"=>65536, "length"=>76}, @s= #false, :length=>false, :pieces=>false, :md5sum=>false, :sha1=>false, :files=>true, :name=>false}, @coerce= {:files=> #}, @dirty=true, @field= {:piece_length=>Integer, :length=>Integer, :md5sum=>String, :pieces=>String, :files=>RubyTorrent::MetaInfoInfoFile, :sha1=>String, :name=>String}, @label= {:piece_length=>"piece length", :length=>"length", :pieces=>"pieces", :md5sum=>"md5sum", :sha1=>"sha1", :files=>"files", :name=>"name"}, @required= {:piece_length=>true, :length=>false, :md5sum=>false, :pieces=>true, :sha1=>false, :files=>false, :name=>true}, @values= {:piece_length=>65536, :length=>76, :pieces=>"r7p\311\030\362\335\030z\212\302\0260\031\035b\311b-`", :name=>"Porp.avi"}>>, :comment=>"Blah!", :announce=>#, :created_by=> "RubyTorrent make-metainfo (http://rubytorrent.rubyforge.org)"}>> From curtis.schofield at gmail.com Mon Feb 7 02:35:15 2005 From: curtis.schofield at gmail.com (Curtis Schofield) Date: Mon Feb 7 02:32:03 2005 Subject: [rubytorrent-devel] Regarding ' info' Bug Message-ID: I think i tracked down the situation. Using RubyTorrent::BitTorrent.new with only a single argument of metainfo leads to a Package being created from 'metainfo.info', and then Package internally calls info again, dieing. invoking like bt = RubyTorrent::BitTorrent.new(dtorrent.metainfo,RubyTorrent:: Package.new(dtorrent.metainfo)) avoids this, but then a new problem is discovered. Unless another argument is passed after the Package there will be an exception as args (in BitTorrent.iniitalize) will be nil. So calling it like RubyTorrent::BitTorrent.new(dtorrent.metainfo,RubyTorrent:: Package.new(dtorrent.metainfo),:ulratelim => 5*1024) with some any argument that get_args would like, will avoid this. I'm not sure about the intended behavior, but i thought i would pass this along. It now seems that i have the Torrent Client connecting to the aversa tracker's announce.. at least it is making a GET request, whether it is properly registered is a whole other story =p.. Thanks! From wmorgan-rubytorrent-devel at masanjin.net Mon Feb 7 14:56:17 2005 From: wmorgan-rubytorrent-devel at masanjin.net (William Morgan) Date: Mon Feb 7 14:53:03 2005 Subject: [rubytorrent-devel] Regarding ' info' Bug In-Reply-To: References: Message-ID: <20050207195616.GG8910@masanjin.net> Excerpts from Curtis Schofield's mail of 7 Feb 2005 (EST): > I think i tracked down the situation. Thanks for the bug reports. They were due to some small silliness on my part. I've fixed these problems in CVS. Please try it and let me know if you have any more problems. -- William From alex at byzantine.no Mon Feb 7 19:48:18 2005 From: alex at byzantine.no (Alexander Staubo) Date: Mon Feb 7 19:45:08 2005 Subject: [rubytorrent-devel] [patch] MetaInfo.from_stream Message-ID: <42080C52.7070600@byzantine.no> This patch fixes a typo in MetaInfo.from_stream. Alexander. -------------- next part -------------- Index: rubytorrent/metainfo.rb =================================================================== RCS file: /var/cvs/rubytorrent/rubytorrent/rubytorrent/metainfo.rb,v retrieving revision 1.8 diff -u -r1.8 metainfo.rb --- rubytorrent/metainfo.rb 7 Feb 2005 19:52:53 -0000 1.8 +++ rubytorrent/metainfo.rb 8 Feb 2005 00:41:24 -0000 @@ -188,7 +188,7 @@ end def self.from_stream(fn) - from_bstream(BStream.new(f)) + from_bstream(BStream.new(fn)) end def method_missing(meth, *args) From eko at softhome.net Mon Feb 7 20:41:29 2005 From: eko at softhome.net (Eko Budi Setiyo) Date: Mon Feb 7 20:42:01 2005 Subject: [rubytorrent-devel] Re: Windows XP,Azureus,ABC,rubytorrent In-Reply-To: <420816C3.10200@byzantine.no> References: <42080C52.7070600@byzantine.no> <42081576.1010103@softhome.net> <420816C3.10200@byzantine.no> Message-ID: <420818C9.6010105@softhome.net> Sory my mistake. I use replay button. Usually replay button will go to the mailling list. some how rubytorrent mailling list is not like that. Hopefully Morgan can fix this regards Eko Alexander Staubo wrote: > Exactly why are you sending this to me and not the RubyTorrent list? > > (In case you used your mail program's reply button to attempt to > create a new thread -- don't do that. It screws up threaded mail > readers.) > > Alexander. > > Eko Budi Setiyo wrote: > >> Already try the pre realease 0.3. >> The rtpeer.rb is working. But I don't know why is take quite a while >> to listen only port 6969. The after that start to scan port >> 6881,6882..etc. >> After that manage to download the file normally. >> As usual I run everything in one PC. Azureus, ABC, and rubytorrent. >> The example on "doc\api.txt" still doesn't work for me. >> >> I am very hapy the rtpeer.rb is working >> >> >> regards >> Eko >> > > From alex at byzantine.no Mon Feb 7 20:48:09 2005 From: alex at byzantine.no (Alexander Staubo) Date: Mon Feb 7 20:44:58 2005 Subject: [rubytorrent-devel] Re: Windows XP,Azureus,ABC,rubytorrent In-Reply-To: <420818C9.6010105@softhome.net> References: <42080C52.7070600@byzantine.no> <42081576.1010103@softhome.net> <420816C3.10200@byzantine.no> <420818C9.6010105@softhome.net> Message-ID: <42081A59.1020607@byzantine.no> It doesn't need fixing, if you understand this: http://www.unicom.com/pw/reply-to-harmful.html Use the "reply to all" button instead. And again, when you want to create a *new* thread, please *don't* use the reply button. Use your mail program's "new message" button. Otherwise threaded email clients like Thunderbird will think your message is a reply, and will nest it as such. Thanks. Alexander. Eko Budi Setiyo wrote: > Sory my mistake. > I use replay button. Usually replay button will go to the mailling list. > some how rubytorrent mailling list is not like that. > Hopefully Morgan can fix this > > regards > Eko > > Alexander Staubo wrote: > >> Exactly why are you sending this to me and not the RubyTorrent list? >> >> (In case you used your mail program's reply button to attempt to >> create a new thread -- don't do that. It screws up threaded mail >> readers.) >> >> Alexander. >> >> Eko Budi Setiyo wrote: >> >>> Already try the pre realease 0.3. >>> The rtpeer.rb is working. But I don't know why is take quite a while >>> to listen only port 6969. The after that start to scan port >>> 6881,6882..etc. >>> After that manage to download the file normally. >>> As usual I run everything in one PC. Azureus, ABC, and rubytorrent. >>> The example on "doc\api.txt" still doesn't work for me. >>> >>> I am very hapy the rtpeer.rb is working >>> >>> >>> regards >>> Eko >>> >> >> > > From eko at softhome.net Mon Feb 7 20:52:44 2005 From: eko at softhome.net (Eko Budi Setiyo) Date: Mon Feb 7 20:53:16 2005 Subject: [rubytorrent-devel] Re: Windows XP,Azureus,ABC,rubytorrent In-Reply-To: <42081A59.1020607@byzantine.no> References: <42080C52.7070600@byzantine.no> <42081576.1010103@softhome.net> <420816C3.10200@byzantine.no> <420818C9.6010105@softhome.net> <42081A59.1020607@byzantine.no> Message-ID: <42081B6C.9030609@softhome.net> I understand now Sory for that eko Alexander Staubo wrote: > It doesn't need fixing, if you understand this: > > http://www.unicom.com/pw/reply-to-harmful.html > > Use the "reply to all" button instead. > > And again, when you want to create a *new* thread, please *don't* use > the reply button. Use your mail program's "new message" button. > Otherwise threaded email clients like Thunderbird will think your > message is a reply, and will nest it as such. Thanks. > > Alexander. > > Eko Budi Setiyo wrote: > >> Sory my mistake. >> I use replay button. Usually replay button will go to the mailling >> list. some how rubytorrent mailling list is not like that. >> Hopefully Morgan can fix this >> >> regards >> Eko >> >> Alexander Staubo wrote: >> >>> Exactly why are you sending this to me and not the RubyTorrent list? >>> >>> (In case you used your mail program's reply button to attempt to >>> create a new thread -- don't do that. It screws up threaded mail >>> readers.) >>> >>> Alexander. >>> >>> Eko Budi Setiyo wrote: >>> >>>> Already try the pre realease 0.3. >>>> The rtpeer.rb is working. But I don't know why is take quite a >>>> while to listen only port 6969. The after that start to scan port >>>> 6881,6882..etc. >>>> After that manage to download the file normally. >>>> As usual I run everything in one PC. Azureus, ABC, and rubytorrent. >>>> The example on "doc\api.txt" still doesn't work for me. >>>> >>>> I am very hapy the rtpeer.rb is working >>>> >>>> >>>> regards >>>> Eko >>>> >>> >>> >> >> > > From contact_us at haltebis.com Mon Feb 7 20:28:03 2005 From: contact_us at haltebis.com (Eko Budi Setiyo) Date: Mon Feb 7 21:27:56 2005 Subject: [rubytorrent-devel] WindowsXP Message-ID: <420815A3.9040605@haltebis.com> Already try the pre realease 0.3. The rtpeer.rb is working. But I don't know why is take quite a while to listen only port 6969. The after that start to scan port 6881,6882..etc. After that manage to download the file normally. As usual I run everything in one PC. Azureus, ABC, and rubytorrent. The example on "doc\api.txt" still doesn't work for me. I am very hapy the rtpeer.rb is working regards Eko From wmorgan-rubytorrent-devel at masanjin.net Mon Feb 7 21:41:40 2005 From: wmorgan-rubytorrent-devel at masanjin.net (William Morgan) Date: Mon Feb 7 21:38:59 2005 Subject: [rubytorrent-devel] [patch] MetaInfo.from_stream In-Reply-To: <42080C52.7070600@byzantine.no> References: <42080C52.7070600@byzantine.no> Message-ID: <20050208024140.GA10521@masanjin.net> Excerpts from Alexander Staubo's mail of 7 Feb 2005 (EST): > This patch fixes a typo in MetaInfo.from_stream. Fixed in CVS. Thank you. -- William From wmorgan-rubytorrent-devel at masanjin.net Mon Feb 7 21:48:05 2005 From: wmorgan-rubytorrent-devel at masanjin.net (William Morgan) Date: Mon Feb 7 21:45:23 2005 Subject: [rubytorrent-devel] WindowsXP In-Reply-To: <420815A3.9040605@haltebis.com> References: <420815A3.9040605@haltebis.com> Message-ID: <20050208024805.GB10521@masanjin.net> Excerpts from Eko Budi Setiyo's mail of 7 Feb 2005 (EST): > Already try the pre realease 0.3. > The rtpeer.rb is working. Great! > But I don't know why is take quite a while to listen only port 6969. > The after that start to scan port 6881,6882..etc. Right now, RubyTorrent only scans the ports 6881 through 6889. It shouldn't be touching 6969. > After that manage to download the file normally. As usual I run > everything in one PC. Azureus, ABC, and rubytorrent. The example on > "doc\api.txt" still doesn't work for me. I've updated that example slightly in CVS, but it should have (mostly) been working before. You do have to give it correct values for 'filename', 'url' and 'dest', of course. It works for me. Can you cut and paste the error messages you're getting? -- William From wmorgan-rubytorrent-devel at masanjin.net Mon Feb 7 22:29:46 2005 From: wmorgan-rubytorrent-devel at masanjin.net (William Morgan) Date: Mon Feb 7 22:26:55 2005 Subject: [rubytorrent-devel] [matz@ruby-lang.org: Re: Performance of CGI::Cookie / SimpleDelegator fix] Message-ID: <20050208032946.GE10521@masanjin.net> Matz claims 1.8.3 might be released in April. If we're lucky, maybe it will have the Windows socket connection fix applied. (Although the patch has been hanging around since last June... but maybe they just needed some prodding. :) ) Then RubyTorrent will be much more usable on Windows. ----- Forwarded message from Yukihiro Matsumoto ----- Date: Tue, 8 Feb 2005 09:32:52 +0900 From: Yukihiro Matsumoto To: ruby-talk@ruby-lang.org (ruby-talk ML) Subject: Re: Performance of CGI::Cookie / SimpleDelegator fix Hi, In message "Re: Performance of CGI::Cookie / SimpleDelegator fix" on Tue, 8 Feb 2005 03:10:09 +0900, benny writes: |just saw this thread on google | |http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/117475 | |apparently this fix didn't make it into ruby 1.8.2: I will merge the fix to 1.8. Apply the patch or wait for 1.8.3 (which will be released in April, hopefully). matz. --- lib/cgi.rb 1 Nov 2004 23:53:48 -0000 1.68.2.9 +++ lib/cgi.rb 8 Feb 2005 00:32:29 -0000 @@ -772,3 +772,3 @@ class CGI # cookie1.secure = true - class Cookie < SimpleDelegator + class Cookie < DelegateClass(Array) ----- End forwarded message ----- -- William From eko at softhome.net Mon Feb 7 22:42:29 2005 From: eko at softhome.net (Eko Budi Setiyo) Date: Mon Feb 7 22:43:02 2005 Subject: [rubytorrent-devel] WindowsXP In-Reply-To: <20050208024805.GB10521@masanjin.net> References: <420815A3.9040605@haltebis.com> <20050208024805.GB10521@masanjin.net> Message-ID: <42083525.7050008@softhome.net> William Morgan wrote: >Excerpts from Eko Budi Setiyo's mail of 7 Feb 2005 (EST): > > >>Already try the pre realease 0.3. >>The rtpeer.rb is working. >> >> > >Great! > > > >>But I don't know why is take quite a while to listen only port 6969. >>The after that start to scan port 6881,6882..etc. >> >> > > > I use TCPView from http://www.sysinternals.com/. That why I know that ruby listenning port 6969 quite a while before starting to scan port 6881 to 6889 >Right now, RubyTorrent only scans the ports 6881 through 6889. It >shouldn't be touching 6969. > > > >>After that manage to download the file normally. As usual I run >>everything in one PC. Azureus, ABC, and rubytorrent. The example on >>"doc\api.txt" still doesn't work for me. >> >> > >I've updated that example slightly in CVS, but it should have (mostly) >been working before. You do have to give it correct values for >'filename', 'url' and 'dest', of course. It works for me. Can you cut >and paste the error messages you're getting? > > > I use filename and dest "exacly the same with rtpeer.rb. I will try again with the updated one then let the list know regards Eko From wmorgan-rubytorrent-devel at masanjin.net Mon Feb 7 22:54:51 2005 From: wmorgan-rubytorrent-devel at masanjin.net (William Morgan) Date: Mon Feb 7 22:51:49 2005 Subject: [rubytorrent-devel] WindowsXP In-Reply-To: <42083525.7050008@softhome.net> References: <420815A3.9040605@haltebis.com> <20050208024805.GB10521@masanjin.net> <42083525.7050008@softhome.net> Message-ID: <20050208035451.GG10521@masanjin.net> Excerpts from Eko Budi Setiyo's mail of 7 Feb 2005 (EST): > I use TCPView from http://www.sysinternals.com/. That why I know that > ruby listenning port 6969 quite a while before starting to scan port > 6881 to 6889 Perhaps it's trying to connect to a tracker on port 6969 on some other machine? If so, then the delay is probably the known Ruby on Windows issue where TCP timeouts freeze the entire program. > I use filename and dest "exacly the same with rtpeer.rb. > I will try again with the updated one then let the list know Ok, thanks. -- William From wmorgan-rubytorrent-devel at masanjin.net Sat Feb 12 19:31:46 2005 From: wmorgan-rubytorrent-devel at masanjin.net (William Morgan) Date: Sat Feb 12 19:28:32 2005 Subject: [rubytorrent-devel] [ANN] RubyTorrent 0.3 (beta) Message-ID: <20050213003146.GA22290@masanjin.net> I'm happy to announce RubyTorrent 0.3, which I've decided is good enough to be called a beta. :) >From http://rubytorrent.rubyforge.org/: RubyTorrent is a pure-Ruby BitTorrent peer library and toolset. You can use it to download or serve files over BitTorrent from any Ruby program. RubyTorrent is released under the GNU GPL. Note that RubyTorrent doesn't include a tracker, although plans are in the works. Nor does it include a fancy client program (though it does include a reasonable one, mostly for debugging). At this point, it's "only" a BitTorrent peer and tracker communication library. Release notes for 0.3: Many more bug fixes. Speed is now basically comparable to Bram's client---at least in my limited experiments. The following are known issues with this release: - Ruby threads don't play well with curses. Non-blocking getch hangs. See [ruby-talk:130620]. So we use ncurses. - Ruby threads don't play well with TCP sockets on Windows. There is a 20-second *global* freeze every time an outgoing connection is made to a non-responsive host. See [ruby-talk:129578], [ruby-core:04364]. As you can imagine, this can be quite a performance hit in a program that can make potentially hundreds of such connections. In fact, it renders RubyTorrent almost useless on Windows. A patch exists (indeed, has existed for many months), and if I bug Matz - Ruby threads don't play well with writing data over TCP sockets. At least, that's what I glean from [ruby-talk:130480], and it might explain the occasional freezing behavior I see (3 to 30 seconds, sporadic) under heavy loads in Linux. Other than that :) everything works. I think. -- William From eko at softhome.net Mon Feb 14 02:56:43 2005 From: eko at softhome.net (Eko Budi Setiyo) Date: Mon Feb 14 02:57:06 2005 Subject: [rubytorrent-devel] RubyToday Project Message-ID: <421059BB.8010001@softhome.net> Hi all, Just like William Morgan releasing rubytorrent 0.3, I also want to share with you all that I am also in process of releasing "rubytoday" project that using "rubytorrent" Please give any comment's. Now I looking to find "bittorent tracker" so that I can do "real demonstration" of rubytoday. Any suggestion where I can get bittorrents tracker service? The RubyToday project website is http://www.rubytoday.com Regards Eko From wmorgan-rubytorrent-devel at masanjin.net Tue Feb 22 08:10:12 2005 From: wmorgan-rubytorrent-devel at masanjin.net (William Morgan) Date: Tue Feb 22 08:06:29 2005 Subject: [rubytorrent-devel] [matz@ruby-lang.org: Re: Performance of CGI::Cookie / SimpleDelegator fix] In-Reply-To: <20050208032946.GE10521@masanjin.net> References: <20050208032946.GE10521@masanjin.net> Message-ID: <20050222131012.GB14402@masanjin.net> Excerpts from William Morgan's mail of 7 Feb 2005 (EST): > Matz claims 1.8.3 might be released in April. If we're lucky, maybe it > will have the Windows socket connection fix applied. (Although the > patch has been hanging around since last June... but maybe they just > needed some prodding. :) ) The patch for non-blocking socket connects under Windows in now in the 1.8 branch of CVS. Which means it will also be in 1.8.3. Whoohoo! -- William