Hopiu/django-admin2
1
0
Fork 0
mirror of https://github.com/jazzband/django-admin2.git synced 2026-04-17 21:31:05 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Add performance goal to docs

Browse source
This commit is contained in:
Daniel Greenfeld 2013-06-09 20:21:35 +02:00
parent 8f2f9fa280
commit eefab2dec4
1 changed files with 1 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
docs/design.rst
View file

@ -20,6 +20,7 @@ Rather than creating yet another project that skins ``django.contrib.admin``, ou
While the internal API for the backend may be drastically different, the end goal is to achieve relative parity with existing functionality in an extendable way:
* Relative functional parity with ``django.contrib.admin``. This is our desire to replicate much of the existing functionality, but not have to worry too much about coding ourselves into an overly-architected corner.
* Ability handle well under high load situations with many concurrent users. This is diametrically opposite from `django.contrib.admin` which doesn't work well in this regard.
* Extensible presentation and data views in such a way that it does not violate Constraint #4. To cover many cases, we will provide instructions on how to use the REST API to fetch data rather than create overly complex backend code.
* Create an architecture that follows the "*Principle of least surprise*". Things should behave as you expect them to, and you should be blocked from making dangerous mistakes. This is the reason for the ImmutableAdmin type.