[optimization] improve massive write performance by optimizing hooks selection profiling on some massive deletion showed up that 2/3 of the time was spent in hooks selection. Those changes make it much more acceptable (through selection is still not negligeable): * use one registry for each event, so we've much less hooks to check when emiting an event as well as no more need for the match_event selector. This required ability to put one appobject into several registries, using a __registries__ class attribute. * check for deprecated .enabled at registry initialization time instead of at selection time A very simple HooksManager class has been reintroduce to choose the right registry on call_hooks. Those optimisations leads to a ~x3 factor of time necessary to delete 16000 entities.

CubicWeb semantic web framework
===============================

Install
-------

More details at http://www.cubicweb.org/doc/en/admin/setup

Getting started
---------------

Execute:

 apt-get install cubicweb cubicweb-dev cubicweb-blog
 cubicweb-ctl create blog myblog
 cubicweb-ctl start -D myblog
 sensible-browser http://localhost:8080/

Details at http://www.cubicweb.org/doc/en/intro/tutorial/blog-in-five-minutes

Documentation
-------------

Look in the doc/ subdirectory or read http://www.cubicweb.org/doc/en/