On 05/05/10 16:01, Derrell Lipman wrote: > > does the model store have a cache, though? (i haven't stumbled > upon any evidence) if so, how do i configure it? (num. objects in > a cache, num. objects in a page, ttl of objects, etc) > > > Yes, there is a cache in the current implementation. In fact, much of > the code is pertaining to handling the cache. > Look at qooxdoo/framework/source/class/qx/ui/table/model/Remote.js for > details, and at > qooxdoo/framework/source/class/qx/ui/table/model/Abstract.js for > specifics of what methods you need to implement. Also, looking at > Christian's contrib project for implementing data binding with > TreeVirtual will likely be enlightening. >
hi derrell, list, i'm sorry, i was not referring to the current remote model of the qx.ui.table.Table, it certainly has a cache :) however, 1) it does not support object expiration, thus, automatic updates. 2) the values are hardwired (50 rows per page, 15 pages max, if memory serves well) my question was, does the model implementation in the new data binding framework support caching of objects on the client side? from what i see, things are too tied to json, thus not really usable for my purposes. i'm sorry if i'm missing someting obvious. best, burak
------------------------------------------------------------------------------
_______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
