Ernst Bunders wrote: > > problems/todo: > > There are some problems to solve yet: > 1 the methods insert(), commit() and removeNode() from MMObjectBuilder > are calling a special method in QueryResultCache: > invalidateAll(). this method simply invalidates all queries containing > steps of a certain type. This runs absulutely counter to the whole > idear of the cache invalidaton system, and must be killed. It is > supposed to be there to make shure (local) queries return the right > content straigt after a database write, but logging shows that this > method is never called before the proper event was handled, so it > should not be necssairy. But somebody has put it there for a reason, > so i would like to know more about it.
I am quite sure that this did happen, and also resulted in problems. E.g. when posting in a forum or so. After the post you could quite well not see your own message because the query was as yet not invalidated. Of course, depending on you mileage, this may or may not happen, because it is a kind of timing issue. If it happens more rudely now than for a broadcasted message it would happen, that that should change, yes. So, whatever may change, I think that local changes must not lead to invalidation only after broadcasting, but must be communicated directly, to ensure that causality remains conserved always. -- Michiel Meeuwissen mihxil' Peperbus 111 MediaPark H'sum [] () +31 (0)35 6772979 nl_NL eo_XX en_US _______________________________________________ Developers mailing list [email protected] http://lists.mmbase.org/mailman/listinfo/developers
