[Seaside] Weight problems of an immortal session

[Markus Kahl]

Hello everyone!

I have a display onto which I want to render stuff. It is rendered by a
browser. The output for that browser I produce with Seaside.
For this when the display goes online it simply opens the start page and the
browser remains there for all eternity (or the device is switched off).
Comet is used to update the display from the server side without any user
input.

Now due to this constellation I have an immortal session.
And during this session's lifetime a great many updaters are created to
update the page at various places.
The immortality of this sessions seems to come at a price.

While I surely don't know all the consequences of it, I at least noticed one
while taking a look at the WACallbackRegistry.
For each created updater the registry holds a reference to the respective
callback.
I assume that this registry won't be cleared for the whole lifetime of the
session.

The display should run for practically for ever, though.
So what do I do?

This is going to be a problem, right?
Can I simply access the WACallbackRegistry's callback dictionary and clear
it?


Regards,

Markus Kahl
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20100519/c7d6fefc/attachment.htm