Re: request.model in public layout

Andy Altepeter wrote:
> Because of REQUEST's getattr magic, request.model or request/model will still 
> work.

Ah, right, that might work indeed - I didn't think of that. I usually 
try to minimize using magic, but in this case it might actuall serve us 
well.

> What I don't understand, though, is why an explicit delete is required _only_ 
> for the public layout?  Shouldn't the potential memory leak happen in other 
> views as well?

You're right, the edit views have the same problem.

Solving that is quite an undertaking though (but maybe the 
afformentioned magic might mitigate the risk). We concluded that for 
this moment it is likely that a busy website has far more "public" 
requests to handle than edit requests and thus is it useful to have this 
more or less easy fix included in Silva now.


regards,
jw

-- 
Jan-Wijbrand Kolman
[email protected]