[Seaside-dev] Configurable current request context variable

[Max Leske]

Hi,

I would like to use a current request context variable that inherits from DynamicVariable in Pharo and not from WADynamicVariable (I don't want to use the exception mechanism). Hence, I'd like to propose that the current request context variable be made configurable through the configuration mechanism. WACurrentRequestContext could dispatch to the concrete variable to ensure backwards compatibility, e.g.

WACurrentRequestContext>>value
	^ self concreteVariable value

(WACurrentRequestContext would no longer inherit from WADynamicVariable and have a default variable, e.g. WAConcreteCurrentRequestContext. Sorry for the bad name :) ).

If no one objects, I can implement the change (I'll probably need contributor access).

I'm looking forward to comments.


Cheers,
Max