At this moment when refreshing page with some widgets like gridedit, session becomes bigger. This is because of make-action which generates unique symbol for the same action every time code executes (on each request).
This can by fixed by some actions identification. Each action should have unique id which works across requests.
(make-action (lambda(&rest args)) "some-action-name") works ok but for internal actions action name should be hard to guess.
Next code should work fine even if we shared application source code. Internal actions will save under same name and name should be hard to guess.
(make-action (lambda(&rest args)) (md5 (format nil "gridedit-render-widget-body-action-1 ~A ~A" (get-universal-time) (random 1000))))
There is a lack in this solution - we should always name actions.
If we could name actions automatically depending on code position it would be great but as I know only sbcl will allow to do this.
At this moment when refreshing page with some widgets like gridedit, session becomes bigger. This is because of make-action which generates unique symbol for the same action every time code executes (on each request).
This can by fixed by some actions identification. Each action should have unique id which works across requests.
(make-action (lambda(&rest args)) "some-action-name")works ok but for internal actions action name should be hard to guess.Next code should work fine even if we shared application source code. Internal actions will save under same name and name should be hard to guess.
There is a lack in this solution - we should always name actions.
If we could name actions automatically depending on code position it would be great but as I know only sbcl will allow to do this.