Andres,
Unfortunately I'm not expert in multiprocessing in Python but the idea
(use threads for plugins and gevent for processing http transactions)
looks pretty good!
06.03.2014 21:12, Andres Riancho пишет:
> Another idea I've been playing with during the last days is to split
> w3af into two
Another idea I've been playing with during the last days is to split
w3af into two different processes:
* Main: plugins run here
* HTTPClient and response parser
Potentially use multiprocessing to connect both using a multiprocesing.Queue.
The reasons to split w3af's architecture in two are:
*
Taras,
On Mon, Jun 4, 2012 at 5:00 PM, Taras wrote:
> Andres,
> geventhttpclient looks very fast HTTP client!
> Did you also try Twisted? Can you make simple comparison in req/s for:
>
> 1. currently used in w3af solution (urllib+threads)
> 2. geventhttpclient
> 3. Twisted
I tried Twisted, not g
Andres,
geventhttpclient looks very fast HTTP client!
Did you also try Twisted? Can you make simple comparison in req/s for:
1. currently used in w3af solution (urllib+threads)
2. geventhttpclient
3. Twisted
> During the last hours I've been trying to find a faster HTTP
> client to integrate
And something even faster... "Requests/sec: 503396.23 , that's crazy."
https://github.com/wg/wrk
But not usable in python ;)
Regards,
On Sun, Jun 3, 2012 at 10:50 AM, Andres Riancho
wrote:
> List,
>
> During the last hours I've been trying to find a faster HTTP
> client to integrate into w3
List,
During the last hours I've been trying to find a faster HTTP
client to integrate into w3af, and also performed some experiments
[0]. After testing some implementations, clients, programming
methodologies, etc. It seems that I've found the winner:
geventhttpclient [1].
With my tests
