- From: <bugzilla@jessica.w3.org>
- Date: Thu, 27 Mar 2014 03:22:34 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17750 --- Comment #29 from Joe Steele <steele@adobe.com> --- 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. If release() is called while building a request, that should definitely be aborted. Or if release() is called after the app has received the response, but before update() has been called, the session should still be torn down and the app can drop the response on the floor. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Thursday, 27 March 2014 03:22:35 UTC