It works but this is likely because you perform concurrent ajax calls. When
a request is processed and session state is enabled, there is a lock so that
the request can access to the session state without having another request
on the same sesion state messing things up...
Do you actually need to read/write session variables ? You could perhaps use
a directive to disable this if not needed. You could also perhaps try to
queue AJAX requests so that you don't have competing AJAX requests at the
same time (or just avoid this design if you can do so)...
---
Patrice
"Shawn Sesna" <(E-Mail Removed)> a écrit dans le message
de news:
9C910EAE-E740-4F9B-A219-(E-Mail Removed)...
> Greetings! I was researching AJAX to provide a solution to displaying
> status
> messages while a long process executed. I found several examples online
> and
> was able to use their code to get a quick application working. However,
> when
> attempting to implement the solution, the AJAX calls weren't updating the
> screen like the examples were and seemed not to fire until after the long
> running process had completed.
>
> I found the only real difference between my application and the quick app
> is
> that I am using Session variables. I added a Session variable to the
> quick
> app and was able to duplicate the behavior.
>
> The quick app I wrote is simple in nature, when the page loads, it begins
> making AJAX calls and updates a div on the page with the current time
> every
> second. A button on the page issues a sleep command on the thread for 10
> seconds. When not using a Session variable, the time continues to update
> after the button is pressed. When using a session variable, the time
> ceases
> to update until the sleep command has expired.
>
> Is there any way to get AJAX to work when using Session variables?