[tor-dev] Torperf implementation considerations (was: Torperf)

Kevin Butler haqkrs at gmail.com
Wed Sep 18 01:49:01 UTC 2013

> Executing scripts and reading stdout/stderr is probably too low-level.
> I think we need a Python/Twisted (or whatever language Torperf will be
> written in) interface for running an experiment and retrieving results.
> You're probably right on stdout/err being too low level, but most
experiments would be reusing the provided implementation, just wrapping
them in a simple manner. Anyway I think there's a language agnostic way to
get this working, without forcing any extensibility on matching Torperfs
language of choice. I've tried to be pretty generic in my attached changes.

> Well, thanks for your input!  As I said above, it would help a lot if
> you added these ideas to the appropriate sections of the design document.
> Please see attached.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.torproject.org/pipermail/tor-dev/attachments/20130918/e174a7e0/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Added-some-ideas-on-extensibility.patch
Type: application/octet-stream
Size: 5477 bytes
Desc: not available
URL: <http://lists.torproject.org/pipermail/tor-dev/attachments/20130918/e174a7e0/attachment.obj>

More information about the tor-dev mailing list