I'm seeing something similar. It seems that connections are sometimes
refused/fail for random reasons. This was worse under swazoo I think and less
bad under Komanche but still occurs for me with some regularity. Of course,
I've got pretty glitchy wireless as my only available network and suspect that
the general network instability may be contributing to the problem. I'm
interested to see how it works when I get a really stable network.
On Wednesday, February 02, 2005, at 10:36AM, Avi Bryant <avi.bryant@xxxxxxxxx>
wrote:
>On Wed, 2 Feb 2005 13:50:37 +0100, Martin J. Laubach <mjl@xxxxxxxxxx> wrote:
>> I just stumbled over a small problem: it seems that sometimes,
>> the icons from the "halo"-view are not displayed and the styles
>> set are not used either.
>>
>> When cutnpasting the URLs for the icons, I immediately get
>> a "This session has expired, you are being redirected to...",
>> which explains, why the browser can't display them.
>
>Hm, that's odd. Static resources (like images and stylesheets) are
>given unique URLs separate from any session - they are, in fact,
>registered at the same level as sessions are, as WADocumentHandler
>instances, in the WAApplication registry. If you're getting an expiry
>message, that means that they've been removed from that registry - but
>this should only happen if the #isActive method of the handler returns
>false, and unlike for WASession which will return false after a
>certain period of inactivity, WADocumentHandler>>isActive *always*
>returns true (which means, incidentally, that you have a very slow
>memory leak if you keep changing stylesheets, because all of the old
>ones will still be accessible).
>
>Hopefully that description will help you somewhat to track this down...
>
>Avi
>_______________________________________________
>Seaside mailing list
>Seaside@xxxxxxxxxxxxxxxxxxxxxxxxxx
>http://lists.squeakfoundation.org/listinfo/seaside
>
>
|
