-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
WASession >> #unregister does signal an error #851
Comments
@marschall could you share your thoughts about this particular problem .... it appears that the only solution involves using keyAtValue: which can be pretty expensive ... alternately one would have to implement a bi-directional bulk reaping cache ... or ??? I'm going to go with keyAtValue: for the time being, because I need to find out if there are any other changes (like WASession |
The session cache in 3.2 is key → value only which makes the implementation much simper (and use a bit less memory). Which means we can't do But there is a simple fix. A session now knows it's id, I just need to override |
self subclassResponsibility
Name: Seaside-Core-pmm.866
Name: Seaside-Session-pmm.184
Name: Seaside-Tests-Core-pmm.308
|
fix a WAGemStoneRunSeasideGems class>>executeGemCommand: bug and adjust the ZnSeasideGemServer class>>serverClass
Ran into this when I clicked on
New Session
button in counter while testing not tranlogged in Seaside3.2 ....Here's the stack (frame 13 is the bad boy) and the arg to #remove: is a WASession instance:
Not exactly clear what needs to happen here, since compatibility needs to be maintained with alternate cache implementations ... or
removeKey:
needs to be used ...The text was updated successfully, but these errors were encountered: