Hi,
I'm sorry but I don't understand your point of view. Shouldn't it involve calling the Web Asset Manager and using behavior.keepalive?
For instance, Joomla core uses this code (in com_content/tmpl/article/edit.php) to keep the session alive when editing articles:
$wa->useScript('keepalive')
->useScript('form.validate')
->useScript('com_contenthistory.admin-history-versions');
So, as far as I can tell, the user's session is kept alive when she is editing an article, so she doesn't get logged out before her changes are saved.
I hope you will consider adding something like this to future versions of Hikashop.
And please forgive me if I've completely missed your point.
In the meantime, I've upped the Session Lifetime in my Global Configuration from 15 to 60 minutes, so hopefully that will be long enough for my applications