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 think it is good idea to make time and resource tests. -- Taras http://oxdef.info ---- "Software is like sex: it's better when it's free." - Linus Torvalds ------------------------------------------------------------------------------ WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd _______________________________________________ W3af-develop mailing list W3af-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/w3af-develop
