As we have discussed before the knop_nav ctype can be rather slow. Jolle has talked about performance problems with the nav->url tag, and when benchmarking a site today I discovered that nav->renderhtml for a not too complex site took 300-400 ms, while 30-40 ms would be acceptable for me. I solved it short term with caching on the finished html level.

It's clear that the nav ctype needs a complete rewrite, possibly introducing a new type replacing nav as we know it since I think it will be difficult to make a new implementation compatible with the old, so the new implementation would get a life side by side with the old, which can be slowly (very slowly) phased out.

At the same time knop_nav is very central to knop as it is responsible for dispatching and keeping track of application flow, so it's important to make the transit smooth.

Just thinking out loud to be open about Knop's weaknesses and future directions.

--
Johan Sölve [FSA Member, Lasso Partner]
Web Application/Lasso/FileMaker Developer
MONTANIA SOFTWARE & SOLUTIONS
http://www.montania.se mailto:joh-n@montania.se
(spam-safe email address, replace '-' with 'a')

#############################################################
This message is sent to you because you are subscribed to
the mailing list <knop@lists.montania.se>.
To unsubscribe, E-mail to: <knop-off@lists.montania.se>
Send administrative queries to <knop-request@lists.montania.se>
List archive http://www.nabble.com/Knop-Framework-Discussion-f29076.html
Project homepage http://montania.se/projects/knop/
Google Code has the latest downloads at http://code.google.com/p/knop/