- From: <bugzilla@jessica.w3.org>
- Date: Thu, 27 Mar 2014 03:35:44 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17750 --- Comment #30 from David Dorwin <ddorwin@google.com> --- (In reply to Joe Steele from comment #29) > Would that use case cause a problem? I could see an app calling update() > which causes a license to be cached and then on receiving release(), > immediately tearing down the session. That should be fine. I assume you mean "cause a license to be stored persistently...". If so, release() would cause it to be erased from persistent storage. release() is *not* close() - it actually releases all resources related to the session. See the discussion starting at Comment 16. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Thursday, 27 March 2014 03:35:49 UTC