All data in a big object ?
Jo Wouters - November 23, 2008 - 23:17
| Project: | Site Documentation |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | postponed (maintainer needs more info) |
Jump to:
Description
I would like to propose a 'redesign' of the code, so all data is first stored in a big object (or array), before it is outputed.
Currently the output of most of the internal functions of this module is html-code, but html-code is only usefull to be printed on a website.
Storing the data in another format (a big object or associated array) before running it through some theming-functions, might make some extra functionality available:
* keeping an eye on all changes in the sitedoc (by comparing previous versions of the object with the latest one)
* making the data available via xmlrpc so a central site can be used to keep an eye on all distributed sites
Would that be a good idea ? i can spend some time programming it.
#1
One of the problems we have now is that the output can be HUGE, especially if one asks for URL aliases. There have been reports of exhausting memory. If this would resolve that, it would be nice.
#2