Commit 40202050 authored by Vincent Pelletier's avatar Vincent Pelletier

Add a TODO entry about handler instances not being always singletons in current code.


git-svn-id: https://svn.erp5.org/repos/neo/branches/prototype3@1167 71dcc9de-d417-0410-9af5-da40c76e7ee4
parent 2cfd0545
...@@ -70,6 +70,12 @@ RC - Review output of pylint (CODE) ...@@ -70,6 +70,12 @@ RC - Review output of pylint (CODE)
The current handler split is the result of small incremental changes. A The current handler split is the result of small incremental changes. A
global review is required to make them square. Consider rename handler global review is required to make them square. Consider rename handler
methods without the 'handle' prefix. methods without the 'handle' prefix.
- Make handler instances become singletons (SPEED, MEMORY)
In some places handlers are instanciated outside of App.__init__ . As a
handler is completely re-entrant (no modifiable properties) it can and
should be made a singleton (saves the CPU time needed to instanciates all
the copies - often when a connection is established, saves the memory
used by each copy).
Storage Storage
- Implement incremental storage verification (BANDWITH) - Implement incremental storage verification (BANDWITH)
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment