On 23/09/15 15:46, Stian Soiland-Reyes wrote:
Agreed about stale results. I guess it could be tricky to invalidate if the
dataset is updated out of bounds (e.g. in a different browser or separate
http calls) - is there a timestamp resource in Fuseki that the UI could
check?
(for some reason emails don't appear to be copied to JIRA - I'm sure
they use to)
Adding e-tags to Fuseki is easy enough (well, corner cases around
transactions long term maybe ... details ...) but to check requires
modification to YASQE/YASR AFAICS.
At the moment they are opaque and delivered as minified JS. Haven't
found a way to poke from outside but the source looks like there are
flags to control persistence which is another option.
From a design point of view, it's not like it is wrong; it's difefrent
use case. Being able to go back and see previous work in a workbook
style is a use case. It's just different from the "explore what is
there" use case.
Andy
