Originally posted on Trac by gaspard Original Trac Ticket
Description (Last modified by gaspard)
All the way when designing zena, I have been fighting against
Rails to take control back.
The parts that I do not need SQL generation (could be all
managed by hand which is already the case in zafu code) macros for
validation, etc (it would be easier to implement my own steps due
to the high dependency to 'Node' class) routes (I use regex
already) caching (I use my own system) The parts I need ajax with
javascript return (RJS like) a clean and lightweight model
implementation (create/ read / update / destroy) fast for small
calls (while doing live editing) small memory footprint concurrency
simple controller (not much code in there already)
Trac Attachments
Trac Comments
2008-02-09 12:22:46 changed by gaspard
status changed from new to assigned.
description changed.
status changed from new to assigned.
description changed.
2008-02-09 14:59:04 changed by anonymous
keywords set to performance.
keywords set to performance.
