[Tahoe-dev] API for tahoe

[Zooko O'Whielacronx]

On Jul 6, 2007, at 7:13 AM, Andy Green wrote:

> Yes I looked at the sources and had an idea of the general structure.
> Foolscap though can equally become a C or C++ library if push came to
> shove, it's not inherently bound to Python AIUI.

That's an interesting possibility.  I'd like to know what Brian  
Warner thinks about it.

> The reason I ask is that if the planets come into alignment I might  
> end
> up with the possibility for an embedded, Internet-connected mass
> deployment of Tahoe.

Could you tell me more (understanding that there is an astrological  
disclaimer)?  Is this a deployment of Penumbra that you're thinking  
about?

>   The platform would be reasonably fast for embedded
> but RAM-constrained, perhaps only 32MB.  And as you suggest Python  
> does
> its best to disallow cross compilation, but it could be forced to  
> do so.
>  Since nobody else is working on a C implementation in the case of
> planetary alignment I guess the first move would be to port python and
> see what happens using stock Tahoe.

I would love to see the results of such an experiment.   
Coincidentally, Brian mentioned yesterday that he wants to get the  
memory-usage measurements fixed (ticket #79, see also #54, #29).

By the way, what Reed-Solomon implementation do you use in Penumbra?   
I updated Prof. Luigi Rizzo's old "fec" library for our zfec module [1].

Regards,

Zooko

[1] http://allmydata.org/trac/tahoe/browser/src/zfec

tickets mentioned in this message:

http://allmydata.org/trac/tahoe/ticket/79
http://allmydata.org/trac/tahoe/ticket/54
http://allmydata.org/trac/tahoe/ticket/29