Taras,
On Mon, May 9, 2011 at 4:26 PM, Taras <ox...@oxdef.info> wrote:
> Andres,
>
>> >>
>> >> Hmmm, I think you are totally right!
>> >> There is no really needing for stringIO and flush() so you are free to
>> >> remove it. Don't forget also fix _loadFromFile() method.
>> >
>> > Changes applied in r4203, lets see if this helps a little bit with
>> > the memory usage of w3af and fixes the bug :)
>>
>> One more question about the history module, why are we storing things
>> in sqlite AND the filesystem? Most information about the request is
>> stored in the DB (except from the body), and then the .trace files
>> hold all the request/response. Is this because of performance
>> concerns? Did you test this same module but with the req/res body
>> stored in the DB?
>
> Yes, it was made in perspective on performance. Currently we keep in
> memory only needed information about HTTP transactions e.g. URI, method,
> response code and so on. When we need to show transaction details e.g.
> response body it is loaded from file. But...we also can do it (loads
> details separately) with DB. As I know Burp also keeps transactions as
> separate files. Do you want to bring it all back to sqlite DB?
I just wanted to understand why you used the .trace files :)
Please take a look at the changes I've introduced in r4218 , I'm
fixing the concurrency issues that the .trace files introduce by using
"file locks". Let me know what you think about this solution that
should fix all those nasty:
(No such file or directory: '/root/.w3af/sessions/target-date/xyz.trace'".)
> I think
> it is good idea to make time and resource tests.
We should measure speed of FileLock vs. sqlite, that would be interesting!
https://sourceforge.net/apps/trac/w3af/ticket/163268
>
> --
> Taras
> http://oxdef.info
> ----
> "Software is like sex: it's better when it's free." - Linus Torvalds
>
>
>
--
Andrés Riancho
Director of Web Security at Rapid7 LLC
Founder at Bonsai Information Security
Project Leader at w3af
------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
W3af-develop mailing list
W3af-develop@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/w3af-develop
