Bug #2510
client-side context reset problem
Status:
Closed
Priority:
Normal
Assignee:
Target version:
Start date:
Due date:
% Done:
0%
billable:
No
vendor_id:
GCD
case_num:
History
#1 Updated by Constantin Asofiei over 9 years ago
- File ca_upd20150131c.zip added
- Status changed from WIP to Review
Attached update fixes the reset of client-side context data, when CTRL-C is pressed and ClientCore.start loop goes to a second iteration.
Passed runtime testing.
#2 Updated by Greg Shah over 9 years ago
Code Review ca_upd20150131c.zip
It looks good. My only question is whether the ContextLocal
should also have its SecurityManager
instance set to null
.
#3 Updated by Greg Shah over 9 years ago
You can go ahead and check it in.
#4 Updated by Constantin Asofiei over 9 years ago
Greg Shah wrote:
You can go ahead and check it in.
Released to rev 10734.
My only question is whether the ContextLocal should also have its SecurityManager instance set to null.
The securityManager is really used only on server-side... but to clear it, we need to keep track of all ContextLocal instances in some kind of registry.
#5 Updated by Greg Shah over 9 years ago
- Target version set to Milestone 12
- Status changed from Review to Closed
Let's not worry about this now. Your update is a good, safe movement forward.
#6 Updated by Greg Shah over 7 years ago
- Target version changed from Milestone 12 to GUI Support for a Complex ADM2 App