> > I hadn't thought of using the cache. In my case, I'm not sure it'll > work since the db is highly dynamic.
What's the difference between passing the results directly to LOAD somehow vs. saving it in the cache and having the component function then retrieve it from the cache? Either way, it's the same set of results. > Sessions won't work either, since > I was interested in passing a db Storage object, not just an index. > By "db Storage object" I assume you mean a DAL Rows object (i.e., the results of a select). Rows objects can be stored in the session, but as of the current stable release, they are stored and retrieved as a list of dictionaries. There's a change in trunk that now stores them as a list of Row objects (actually, technically the Row objects themselves are stored as dictionaries, but upon retrieval, they are converted back to Row objects, though without the .update_record() and .delete_record() methods available). So, using trunk, you may find everything works fine storing the Rows object in the session. Anthony
