[Seaside] Caching session on canvas?

[Boris Popov]

Thanks for the hint, I think I'll do a combination of two actually. Its
gotten to the point where using notification to find a session started
showing up in profiles of largish/complicatedish reports (~8
microseconds per call adds up).

Cheers,

-Boris

-- 
+1.604.689.0322
DeepCove Labs Ltd.
4th floor 595 Howe Street
Vancouver, Canada V6C 2T5

boris at deepcovelabs.com

CONFIDENTIALITY NOTICE

This email is intended only for the persons named in the message
header. Unless otherwise indicated, it contains information that is
private and confidential. If you have received it in error, please
notify the sender and delete the entire message including any
attachments.

Thank you.

-----Original Message-----
From: seaside-bounces at lists.squeakfoundation.org
[mailto:seaside-bounces at lists.squeakfoundation.org] On Behalf Of Avi
Bryant
Sent: Wednesday, October 25, 2006 2:08 PM
To: The Squeak Enterprise Aubergines Server - general discussion.
Subject: Re: [Seaside] Caching session on canvas?


On Oct 25, 2006, at 1:57 PM, Boris Popov wrote:

> I've been thinking of removing the cost associated with lookup of a
> current session by caching it on a canvas when its created in
> WAPresenter>>renderWithContext: are there any gotchas I might be
> missing?

If you're going to cache it, you might as well do that at the  
RenderingContext level rather than on individual canvases (since a  
new canvas is created for each component).

Or you could cache it in each component - I (at least) tend to use  
"self session" on components most often.

I can't think of any gotchas with any of this.  None of these objects  
should ever be moving between sessions.

Avi
_______________________________________________
Seaside mailing list
Seaside at lists.squeakfoundation.org
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside