> Especially when it leads to 'OR' queries though. This should not happen
> in a clear cloud model, and it is advicable to explicitely avoid it
> using 'searchdirs' otherwise. But still, the extra 'depth' of the query
> is sometimes undesirable. We agree on that :-)
still, most queries in a typical mmbase application are very cachable,
and should be cached. Allso, normally query execution time should stay
below 10 - 15 millisecs, or else you have trouble with your indexes, or
with your queries (or you are stuck with some totally useless database
inheritance scheme :-) ). Presently i don't feel query times to be an
actual problem (unlike update times).
Is the caching framework ready to do stuff like forums?
This is particularly unfortunate becouse mmbase nodes can not be used in
combination with jstl and expression language, as methods such as
node.getStringValue("name") are not supported bij expression language.
This stands in the way of using mmbase for building mvc webapps.
I think it's OK to use taglibs to get the data that needs displaying,
the jsp should just not use request parameters do define what it
should be showing.
_______________________________________________
Developers mailing list
[email protected]
http://lists.mmbase.org/mailman/listinfo/developers
