4 Feb
2017
4 Feb
'17
7:30 p.m.
Hi BaseX community, I'm wondering whether there is the possibility to keep some kind of in-memory state among successive RestXQ invocations. I know I could use the session object but this comes at the risk of loosing the state at session expiration. I could of course use a DB but with this solution I'm not sure that paying the overhead of accessing a database is worth for the small checks I need to perform. I was thinking of using Java and create some sort of singleton but this would introduce an unnecessary dependency from a custom jar. Maybe with the Jobs module? Any other clue? Thanks, Marco.