seaside-dev March 2012

seaside-dev@lists.squeakfoundation.org

6 participants
6 discussions

cookie based sessions, RESTful urls no _k
by Nick Ager 22 Nov '12

22 Nov '12

Hi, In RESTful applications which also generate continuation key (_k) links a problem can arise if you open multiple tabs all sharing the same session. To illustrate: 1) Enable cookies for http://localhost:8080/examples/counter. 2) Open the counter and increment the value. 3) Open http://localhost:8080/examples/counter in a new tab and decrement the counter. 4) Return to the first counter and increment the value - you will see "-1" rather then "2" ! What I think is happening: If Seaside finds a session but there is no continuation key (_k) then WASession>>#handleFiltered: calls WARenderLoopMain>>#start which in turn creates a new root presenter and calls #initialRequest on the presenter. When the second tab is opened a new WACounter is created and stored in the session's #presenter property. When you return to the first tab, the callback is executed on the first counter, but the second counter is rendered. Ideas for possible fixes: * I thought that #presenter was backtracked so don't understand why the original counter #presenter isn't restored for the callback. If the presenter was backtracked correctly then the counter example should work as anticipated.... however: * in Pier (and potentially other RESTful apps) you don't want to create a new presenter for every RESTful call within an active session. If you don't create a new presenter then #initialRequest currently won't be called, which then won't allow your RESTful app to derive state from the url. If Seaside is modified to call #initialRequest do you need to differentiate between a call on a newly created session and one on an existing session? You could differentiate with a call to a new method on WAPresenter, pass in a flag to #initialRequest, or set a WARequestContext property to indicate a new session had been created. What to do with backtracked state. Do you nil all state before handling the request, restore state from a stored "initial value" snapshot or just use the state of the components from their last handled state? I bought this issue up before [1], but didn't pursue it as I was struggling to understand the issues and ran out of time. Julian responded to my previous email when I was proposing a problematic fix with: I'm not sure it's a good fix in the general case. If you don't have a > continuation key, you shouldn't (by definition) have any existing > (backtracked) state. Relying on the root presenter currently in the > Session is problematic since that value is backtracked for each > request; you'll simply get whichever root happened to be used by > whatever request was last handled by that session. If you don't happen > to be ever changing the root, then it may well be what you want, but > it's not right in the general case. > Incidentally, this also touches on the flaw I was discussing the other > week with our snapshots: because we have no continuation key, we > really ought to nil out any backtracked data before processing the > request (at least that way we have a consistent state while handling > the request). We don't run into the problem with the root presenter > because #start reinitializes it, but for other backtracked state, > you'd just get random stuff in there based on the last-handled > request. > A more appropriate general fix (at least in this case) could be to > take the last-used continuation and apply its state before handling a > request with no _k. However, we don't always know the last-used > (depending on the caching mechanism in place) and I'm not convinced > that is actually always what people want. I still feel pretty > confident that the "right" semantics of an Application/Session request > with no _k is to start a new main/render-loop. Certainly for Pier as it is currently designed I don't think that creating a new render-loop for session requests with the _k is the right thing to do, as it created a new root #presenter. I think ideally Seaside would for existing session with no _k 1) Keep the existing #presenter 2) call #initialRequest with a flag to indicate that a new session hadn't been created. 3) restore the state to an "initial render state" which is snapshotted (?) when the initial render occurs on a new session. Thoughts Nick [1] http://forum.world.st/sessions-continuation-keys-restful-urls-and-component… If each tabs starts with a RESTful url then a new presenter will be created.

3 4

Seaside 3.0.7
by Philippe Marschall 31 Mar '12

31 Mar '12

Hi Nick was kind enough to fix Issue 267 [1] and we once again a nice collection of fixes [2]. Nick ideally needs a 3.0.7 release. I propose he does it :-). [1] http://code.google.com/p/seaside/issues/detail?id=267 [2] http://code.google.com/p/seaside/wiki/Seaside307Changelog Cheers Philippe

4 29

Re: [Pharo-project] [Pharo 1.4] Please test!
by Nick Ager 30 Mar '12

30 Mar '12

Trying the soon to be released 3.0.7: Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSeaside30'; load. (ConfigurationOfSeaside30 project version: '3.0.7') load: 'OneClick'. I see the following issues during loading: RBAddMethodChange>>printOn: (RBPlatform is Undeclared) RBCommentChange>>primitiveExecute (RBPlatform is Undeclared) RBCommentChange>>printOn: (RBPlatform is Undeclared) OBDefinition>>doItReceiver (FakeClassPool is Undeclared) WAScreenshot>>toggleUIProcess (Project is Undeclared) WAScreenshot>>toggleUIProcess (Project is Undeclared) WAScreenshot>>toggleUIProcess (Project is Undeclared) WAScreenshot>>toggleUIText (Project is Undeclared) Evaluated -> Seaside-Core >> seaside304DoIts Form>>writerForMimeType: (PCXReadWriter is Undeclared) http://code.google.com/p/seaside/issues/detail?id=719 Cheers Nick On 30 March 2012 15:08, Scott Gibson <wsgibson(a)windstream.net> wrote: > I am not sure of the plans for syntax highlighting in version 1.4 but when > I go to Settings for Shout: Syntax Highlighting I am not given any controls > to adjust the values. When I change try to make the changes > programmatically (as in 1.3) I am given the error AnObsoleteSHStyleSetting. > Is this functionality being removed or has it been replaced perhaps? > > Thanks! > Scott Gibson > > On Mar 30, 2012, at 3:26 AM, Marcus Denker wrote: > > > > > > > You can download the lastest 1.4 here for testing: > > > > > https://ci.lille.inria.fr/pharo/view/Pharo%201.4/job/Pharo%201.4/lastSucces… > > > > And a first version of the one-click here: > > > > > https://ci.lille.inria.fr/pharo/job/Pharo%20One%20Click%20image/lastSuccess… > > > > > > > > > > -- > > Marcus Denker -- http://marcusdenker.de > > > > > > >

2 1

WAProfilerItem>>#tree
by Paul DeBruicker 29 Mar '12

29 Mar '12

In the attached file-out I included a version of WAProfilerItem>>#tree that prints % and times: 8.3% {22ms} JQAjax>>script: |8.3% {22ms} JQAjax(JSObject)>>script:on: | 8.3% {22ms} JSScript(JSObject)>>javascriptOn: | 8.3% {22ms} JSScript>>javascriptContentOn: | 8.3% {22ms} GRNullCodecStream(GRCodecStream)>>javascript: | 8.3% {22ms} JQueryInstance(JSObject)>>javascriptOn: | 8.3% {22ms} JSCall>>javascriptContentOn: | 8.3% {22ms} JSStream class>>encodeArguments:on: | 8.3% {22ms} GRNullCodecStream(GRCodecStream)>>javascript: | 8.3% {22ms} ByteString(String)>>javascriptOn: | 8.3% {22ms} JSStream class>>encodeString:on: | 3.8% {10ms} primitives | 2.3% {6ms} Character>>greaseInteger | 1.5% {4ms} GRNullCodecStream>>nextPut: rather than: 0 JQAjax>>script: |0 JQAjax(JSObject)>>script:on: | |0 JSScript(JSObject)>>javascriptOn: | | 0 JSScript>>javascriptContentOn: | | 0 GRNullCodecStream(GRCodecStream)>>javascript: | | 0 JQueryInstance(JSObject)>>javascriptOn: | | 0 JSCall>>javascriptContentOn: | | 0 JSStream class>>encodeArguments:on: | | 0 GRNullCodecStream(GRCodecStream)>>javascript: | | 0 ByteString(String)>>javascriptOn: | | 4 JSStream class>>encodeString:on: | | 2 GRNullCodecStream>>nextPut: | | 2 Character>>=

2 1

WAQwaqProfilerItem
by Paul DeBruicker 29 Mar '12

29 Mar '12

In the SystemProfilerPharo repository on squeaksource I added code to be able to use the Qwaq profiler inside Seaside.

2 2

How portable is the Fraction class?
by Philippe Marschall 02 Mar '12

02 Mar '12

Hi In Pharo 1.4 both Integer and Fraction answer #isFraction with true. Therefore GRPlatformTest >> #testSeconds fails. A proposes work around is to use to use isKindOf: Fraction instead of #isFraction. How portable is this? Does anybody not have a Fraction class? Cheers Philippe

3 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

seaside-dev March 2012