Also spracht Lalo Martins (Fri, 15 Feb 2008 06:20:22 +0000):
> (Now, on my original design, web pages would be "transient views",
> meaning, there is a ViewImplementation that writes to the WebRequest,
> but it never actually returns a View.  This feature has been lost on
> Peter's implementation, but we plan to bring it back later on; just not
> a very high priority.  For now, by not attaching the View to any site,
> the ViewImplementation can make sure it's collected in the next gc
> cycle.)

Er, except we have no gc at the moment :-D so even things like the 
WebRequest object will just linger forever in the Site's vobjectTable 
until the process is restarted.

I went ahead and re-added transient views, essentially by moving the 
createView() logic from the ViewFactory to the ViewImplementation, where 
it can be overridden.  But that means I'll still be leaking WebRequest 
objects.  Is it as simple as adding a Site.releaseVobject(vw) method (to 
delete vw from the vobjectTable, therefore allowing the refcount to 
eventually reach 0)?  Or am I missing some implications?  I know later on 
we want to have a smarter, proper gc, but for the simple case...

                                               Lalo Martins
      So many of our dreams at first seem impossible,
       then they seem improbable, and then, when we
       summon the will, they soon become inevitable.
GNU: never give up freedom    

vos-d mailing list

Reply via email to