[Twisted-Python] tor hidden service endpoint parser returns a deferred

David Stainton dstainton415 at gmail.com
Sat May 3 00:45:10 UTC 2014


Thanks. Sure thing. Yes I have every intention of contributing
endpoint parsers to txtorcon and txsocksx for use with tor.
Both of these could make it much easier for developers to make their
applications tor friendly.

The endpoints/endpoint parsers api is brilliant! When the tor
client/server endpoint parsers are complete then Tahoe-LAFS for
instance can simply use these endpoints without any code changes at
all. Of course I'm not saying that is all that is required for
Tahoe-LAFS to be "tor friendly"... we have detailed other
considerations in trac tickets:
https://tahoe-lafs.org/trac/tahoe-lafs/ticket/517
http://foolscap.lothar.com/trac/ticket/203

I'm starting to think about the deployment issues... Perhaps someone
on the list knows of the "correct" setup.py (distutils/setuputils?)
procedure to deploy twisted plugins? I shall have to research this
soon. For now my hacky development/testing flow works OK.


On Fri, May 2, 2014 at 9:18 PM, Glyph Lefkowitz <glyph at twistedmatrix.com> wrote:
>
> On May 2, 2014, at 6:59 AM, David Stainton <dstainton415 at gmail.com> wrote:
>
> Today I wrote an endpoint parser for Meejah's txtorcon Tor Hidden
> Service endpoint.
>
>
> This is fantastic.  Basically this is _exactly_ the use-case that we had in
> mind when designing the endpoint parser plugin APIs.
>
> Thanks so much for doing it.
>
> (I hope you'll contribute it to txtorcon when you're done...)
>
> -glyph
>



More information about the tahoe-dev mailing list