[OpenDHT-Users] put_removable not working with Ruby

Alyed Tzompa alyed.tzompa@simitel.com
Sun, 30 Apr 2006 21:35:13 -0700


This is a multi-part message in MIME format.

------_SmarterMail_NextPart_3205170000777210
Content-Type: text/plain;
	charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

=0D=0A=0D=0A				Hi there!=0D=0A=0D=0AI'm having problems making a "put_remo=
vable" (actually not even a "put" works for me) to openDHT. I'm using Ruby =
1.8.4-16 and get the following message:=0D=0A=0D=0Ajava.lang.NoSuchMethodEx=
ception: bamboo.dht.Gateway$XmlRpcPutRemovableHandler.put_removable(java.la=
ng.String, java.lang.String, java.lang.String, java.lang.String, int, java.=
lang.String, java.lang.String, java.net.InetSocketAddress, bamboo.util.Curr=
y$Thunk1)=0D=0A=0D=0ASearched on the mailing list but only found a similiar=
 problem whose solution was placing the parameters in the correct order. I'=
ve checked mines (Key,Value,"SHA",hashed_secret,TTL, Appl_name) but keep on=
 receiving the same message.=0D=0A=0D=0AAny ideas?=0D=0A=0D=0AAlyed=0D=0A=
=0D=0A--------------------------------------=0D=0A#code extract=0D=0A=0D=0A=
dhtServer =3D XMLRPC::Client.new("169.229.50.15","/",5851)=0D=0AdhtKey64 =
=3D Base64.encode64(dhtKey)=0D=0AdhtValue64 =3D Base64.encode64(dhtValue) =
=0D=0A=0D=0A				begin=0D=0A=0D=0AdhtStatus =3D dhtServer.call("put_removabl=
e",dhtKey64,dhtValue64,"SHA",secret.toSha,60.to_i,"my_app")=0D=0A  rescue X=
MLRPC::FaultException =3D> error=0D=0A  puts error.faultCode=0D=0A  puts er=
ror.faultString=0D=0A=0D=0Aend=0D=0A----------------------------------=0D=
=0A=0D=0A

------_SmarterMail_NextPart_3205170000777210
Content-Type: text/html;
	charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

=0D=0A		<p>=0D=0A				<font face=3D"arial" size=3D"2">Hi there!<br /><br />I=
'm having problems making a "put_removable" (actually not even a "put" work=
s for me) to openDHT. I'm using Ruby 1.8.4-16 and get the following message=
:<br /><br />java.lang.NoSuchMethodException: bamboo.dht.Gateway$XmlRpcPutR=
emovableHandler.put_removable(java.lang.String, java.lang.String, java.lang=
.String, java.lang.String, int, java.lang.String, java.lang.String, java.ne=
t.InetSocketAddress, bamboo.util.Curry$Thunk1)<br /><br />Searched on the m=
ailing list but only found a similiar problem whose solution was placing th=
e parameters in the correct order. I've checked mines (Key,Value,"SHA",hash=
ed_secret,TTL, Appl_name) but keep on receiving the same message.<br /><br =
/>Any ideas?<br /><br />Alyed<br /><br />----------------------------------=
----<br />#code extract<br /><br />dhtServer =3D XMLRPC::Client.new("169.22=
9.50.15","/",5851)<br />dhtKey64 =3D Base64.encode64(dhtKey)<br />dhtValue6=
4 =3D Base64.encode64(dhtValue)</font>=0D=0A		</p>=0D=0A		<p>=0D=0A				<fon=
t face=3D"arial" size=3D"2">begin<br /></font>=0D=0A				<font face=3D"arial=
" size=3D"2">=0D=0A						<br />dhtStatus =3D dhtServer.call("put_removable"=
,dhtKey64,dhtValue64,"SHA",secret.toSha,60.to_i,"my_app")<br />=A0 rescue X=
MLRPC::FaultException =3D&gt; error<br />=A0 puts error.faultCode<br />=A0 =
puts error.faultString<br /><br />end<br />--------------------------------=
--<br /><br /></font>=0D=0A		</p>=0D=0A		<br />=0D=0A

------_SmarterMail_NextPart_3205170000777210--