On 2005-02-14 15:16:42, Edi Weitz wrote:
On Mon, 14 Feb 2005 08:56:40 -0500, Zach Beane xach@xach.com wrote:
But it occurred to me that there is already the *request* structure. Would it make sense to be able to have a table of arbitrary keys and values in the request structure for application use? I was thinking of an accessor like this:
I'm wondering if what you really want isn't just per-session info. If in your CURRENT-USER function you replace REQUEST-DATA with SESSION-VALUE isn't that the info you'd like to have? You'd get the sessions for free.
I'm sitting at a similar problem. One function is called two times and has to read some data. It would be nice if I could cache this data for one request so it only has to be read one time.
Can't use a closure because AFAIK one request doesn't always start a new process and the data could be too old in further requests.
I don't want to start a session at this time.
Or maby just two variables in a closure. One holds the data and the other *REQUEST*. Then I check against *REQUEST* with EQ and I know if the stored data is from an old request or the current one. Am I right?
Regards, Stefan