[tahoe-dev] Ruby WebAPI Client & Beta Testers Wanted

[Ian Levesque]

> I looked at both
> libraries (yours and mine), and I see both advantages and  
> disadvantages in
> each of them. Maybe we could somehow merge the good ideas together  
> to make one
> "perfect" Tahoe Ruby lib.


Agreed.  I would be interested in doing that.

Thanks,
-Ian

On Mar 26, 2009, at 9:31 AM, David Triendl wrote:

> On Thu, Mar 26, 2009 at 02:21:21AM -0400, Ian Levesque wrote:
>> Hi Tahoe-Dev,
>>
>> 1. I know you're big Python fans around here, but I finally factored
>> out and BSD-licensed a Ruby client library (with full unit tests) for
>> Tahoe's WebAPI from one of my upcoming products.  The code is here:
>>
>> http://github.com/ianlevesque/rubytahoe
> I also started working on a Tahoe API to Ruby interface (had I only  
> known
> before that you would release one :D), you can find it at
> http://github.com/soult/ruby-tahoe/
>
>> 2. I would love to see this library grow into a "fully supported"
>> front-end library for Tahoe application developers, but it's not  
>> there
>> yet.  At present it works great for all basic operations (see the  
>> unit
>> tests), but is basically cap-ignorant.  You provide a directory  
>> write-
>> cap upon initialization and all operations from then on are path- 
>> based
>> relative to that write-cap. It's easy & convenient but doesn't really
>> take full advantage of Tahoe.  I could use suggestions in this
>> department.
> An official Ruby interface to tahoe would be sweet. (Well, an  
> interface to
> Tahoe in any programming language would actually be sweet). I looked  
> at both
> libraries (yours and mine), and I see both advantages and  
> disadvantages in
> each of them. Maybe we could somehow merge the good ideas together  
> to make one
> "perfect" Tahoe Ruby lib. Some things I really like about your  
> library are the
> very small code size, while you still not depend on non-standard  
> libraries (my
> library currently requires the rest library from
> http://rest-client.heroku.com/), the easy interface and the  
> production grid
> helper that converts username and password to the API url. On the  
> other hand I
> suggest to use classes for files and directory. That way you could  
> also easily
> make the library aware of caps and e.g. allow attaching read-only  
> versions of
> a directory to some other directory.
>
> If you are interested in working on the Ruby interface you can also  
> contact me
> off-list.
> _______________________________________________
> tahoe-dev mailing list
> tahoe-dev at allmydata.org
> http://allmydata.org/cgi-bin/mailman/listinfo/tahoe-dev