Catrina, as I see it, the only way to reliably refresh a cache on the server is to kill the sessions. Once the cache is refreshed, different data is being served. Therefore sessions to the old cache have to be terminated to make sure there are no inconsistencies between data before and after the cache refresh.
Perhaps you mean the browser cache? Or do you have a specific case where a problem arises? -- Scott On Oct 25, 2:48 pm, Catrina <[email protected]> wrote: > This would cause interference with other users though. If other users > are in the Hierarchy tool, then their sessions in TBLive will end. > Okay, thanks. I'll see if there's something else we can work out > here. > > ~Catrina > > On Oct 20, 12:12 pm, Scott Henninger <[email protected]> > wrote: > > > Catrina; There isn't a way to specifically refresh the cache in TBL. > > Using Reset, which can be called programmatically with the URLhttp://[server > > name]:[port]/tbl/sp_reset, should work adequately. > > > -- Scott > > > On Oct 19, 8:46 am, Catrina <[email protected]> > > wrote: > > > > Is there a way to refresh the cache in TBLive programmatically? > > > Possibly throught a SPARQLMotion script? We are currently using the > > > cacheAll configuration in Live. > > > > Thanks, > > > Catrina- Hide quoted text - > > > - Show quoted text - -- You received this message because you are subscribed to the Google Group "TopBraid Suite Users", the topics of which include TopBraid Composer, TopBraid Live, TopBraid Ensemble, SPARQLMotion and SPIN. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/topbraid-users?hl=en
