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
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 <wmorgan-rubytorrent-devel@masanjin.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
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 6889Perhaps 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 knowOk, thanks. -- William <wmorgan-rubytorrent-devel@masanjin.net>