From: Alan Johnson <alan.wayne.johnson@...>
Date: 2008-11-18T18:30:55+09:00
Subject: Re: Does SOCKSSocket work?

------=_Part_16121_32779188.1227000869046
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On Mon, Nov 17, 2008 at 7:10 PM, Yukihiro Matsumoto <matz@ruby-lang.org>wrote:

> Hi,
>
> In message "Re: Does SOCKSSocket work?"
>     on Tue, 18 Nov 2008 09:15:04 +0900, "Alan Johnson" <
> alan.wayne.johnson@gmail.com> writes:
>
> |I am having trouble with class SOCKSSocket.  I am trying to get the
> |following minimal example to work:
> |require 'socket'
> |s = SOCKSSocket.new('www.google.com', 80)
> |
> |Running this I get:
> |$ ruby example.rb
> |example.rb:2: uninitialized constant SOCKSSocket (NameError)
> |
> |First, I assume that SOCKS support must be compiled into ruby, but I
> cannot
> |determine which set of compile flags enables it. Second, looking at the
> ruby
> |source code, it appears that the only SOCKSSocket methods that are even
> |defined are initialize and close, which makes me wonder how it could
> |possibly work.
>
> First, you have to specify --enable-socks=true to configure (or
> extconf.rb run) with libsocks installed.
>
> Second, that's OK, SOCKSSocket inherits everything else from
> TCPSocket.  I myself have not tested SOCKSSocket for a while,
> but I assume it still works.
>
>                                                        matz.
>
>
Thanks for the nudge in the right direction.  Everything is working great
now. To
answer the question in the subject -- yes, SOCKSSocket works, except the
Net::FTP usage of it is broken in the trunk (patch submitted to ruby-core).

-- 
Alan

------=_Part_16121_32779188.1227000869046--