[Zope] FSSession atomicity?

[Curtis Maloney]

On Thu, 13 Apr 2000, Pavlos Christoforou wrote:
> On Wed, 12 Apr 2000, Curtis Maloney wrote:
> 
> > So, if the user logs in correctly, they are redirected to whence they came,
> > which would normally shunt them off to another page.  Would I be correct in
> 
> I believe that a RESPONSE.redirect will first commit the current
> transaction before redirection (I should check the source code), in which
> case the FSSession contents would be available.
> 
> > assuming that the cookie being set is a good indicator of a new transaction
> > beginning?  or one ending?
> 
> Yes, good idea. A cookie will only be set when a transaction commits.
> Check if the cookie is there after the redirection occurs. 

Well, being the curious (and maybe a little paranoid :) type, I have 'ask' set
on my cookie options, so I see every time it tries to set one.

When you log in in this circumstance, two cookies get set (once for the verify
page, once for the page it redirects you to).

Oh, and yes... <dtml-call FSSession> is in the standard_html_header, since it
uses FSSession data (as i showed previously)

So.. If the cookie means it IS commiting, i'm left wondering why the
information isn't showing up.  When a redirect occurs, is it possible the
browser is making the new request on another thread, which _sometimes_ beats
out the 'commiting' thread?  Or is commiting completed before the cookie is set?

> 
> Pavlos
> 
-- 
Have a better one,
	Curtis.

<dtml-var standard_work_disclaimer>