Re: State Threads

[Georg Bauhaus <sb463ba@l1-hrz.uni-duisburg.de>]

Wojtek Narczynski <wojtek@power.com.pl> wrote:
: Georg Bauhaus <sb463ba@l1-hrz.uni-duisburg.de> wrote in message news:<chi2uq$4tp$1@a1-hrz.uni-duisburg.de>...
: 
:> If a user at a client computer decides to open another view of
:> some page in a web based application (a tab, a window), would that lead
:> to the creation of another thread? If not, can thread data safely be used
:> to react to input from either view?
: 
: Please read this introductory paper:
: http://state-threads.sourceforge.net/docs/st.html

I have, and I think it doesn't address the question.
I'm not saying it has to, but the mechanism seems as incomplete
for Web based applications as many others. (Maybe I haven't read
with enough attention, though.)

For example, HTTP is essentially stateless.
Some port receives the input sequence i1, i2, then
i1 _again_. Let ik stand for some Web form.
i1 has triggered a state change in the server's store.
This state change might affect the server's reaction to i2 arriving.
("Go this way if i1 has been X, that way if i1 has been Y").
Now i1 arrives again (user has pressed some back navigation button say).
Only this time i1 carries slightly different data.
Again, this should affect the server's reaction to a possible i2.
Now the previous rule setting (based on previous i1) for reacting to i2
is outdated, unless the server updates all affected storage in the server.
What if i2 arrives another time now?

-- Georg