List,
One of my enhancements for future versions of w3af is to start
using a real ORM inside w3af [0] and while I'm thinking about it I
would like your inputs. For those who don't know exactly where the ORM
would be used, here is a summary:
* HTTP requests and responses (at least the meta-data, not the body)
* Lists and sets which are stored in disk instead of memory
If we add a real ORM to w3af we would get these benefits:
* Less code we need to maintain
* Replace our custom ORM with something tens of thousands
other developers use. Much more tested and maintained
* Potentially fix issues like [1] which I haven't been able to
fix for at least 2 years
And the cons are:
* One more dependency, but hopefully we'll find something that
is pure python or very easy to install on all platforms. (Starting to
think like you Taras!)
Ideas?
[0] https://github.com/andresriancho/w3af/issues/1274
[1] https://github.com/andresriancho/w3af/issues/1080
Regards,
--
Andrés Riancho
Project Leader at w3af - http://w3af.org/
Web Application Attack and Audit Framework
Twitter: @w3af
GPG: 0x93C344F3
------------------------------------------------------------------------------
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works.
Faster operations. Version large binaries. Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
_______________________________________________
W3af-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/w3af-develop
