With "threadsafe" I mean is the DAL threadsafe developed? There are
several requests maybe calling this DAL and this must be thread safe!

If I want to be "thread safe" I will call the next time from the
callback of the other request, like I have done in my example above.
This will prevent the web browser to run two identical requests at the
same time (a maximum of 2 concurrent restricted by the http protocol).

Regards,
Michael



On 5/11/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> << The code is threadsafe ???????
>
> There is a very good chance that it is NOT threadsafe and all of the
> symptoms point to a threading race condition.
>
> Theory says you can't have thread safety without an atomic lock
> administered by the control system -  the browser engine in this case.
> Simply checking a variable for "unset" before launching a new request is
> not sufficient.
>
> And an Async call implies multiple overlapping  threads.
>
> The fact that it behaves differently in FireFox and IE but still happens in
> both just illustrates the different race condition inside the two browser
> engines.
>
> You have to have some sort of lock & monitor mechanism.
>
> So, how does AjaxPro or I.E. / Firefox provide the lock and the monitor
> functionality?
> Does anyone know the details?
>
> This must be an issue for Atlas also - how do they deal with this problem?
>
>
> Gregg Teehan
> phone:      (510) 770-4548
> pager:      (510) 744-7162
>
>
>
>
>             "[EMAIL PROTECTED]
>             .com"
>             <[EMAIL PROTECTED]                                          To
>             .com>                     "Ajax.NET Professional"
>             Sent by:                  <[email protected]>
>             [EMAIL PROTECTED]                                          cc
>             ups.com
>                                                                   Subject
>                                       [ajaxpro] Re: Ajax Async Call Stops
>             05/11/2006 09:32          Responding
>             AM
>
>
>             Please respond to
>             [EMAIL PROTECTED]
>                  ups.com
>
>
>
>
>
>
>
> The code is thread safe becuase it will never do two concurrent calls
> at the same time due to the wallCallback variable. The problem with the
> method you described is that it will halt my entire javascript routine
> if there is a missed callback. My upload page javascript needs to check
> to see if the upload is completed regardless if it failed to receivea a
> callback.
>
> I was not able to reproduce the problem in IE, however if you use
> Firefox it will stop responding after a while.
>
> Loop Count: 988
> Callback: 5/11/2006 9:29:41 AM - Last: 566
>
>
>
>
> ______________________________________________________________________
> This email has been scanned by the NUMMI Email Security System.
> ______________________________________________________________________
>
>
>
> ______________________________________________________________________
> This email has been scanned by the NUMMI Email Security System.
> ______________________________________________________________________
>
> >
>


-- 
Best regards | Schöne Grüße
Michael

Microsoft MVP - Most Valuable Professional
Microsoft MCAD - Certified Application Developer

http://weblogs.asp.net/mschwarz/
http://www.schwarz-interactive.de/
mailto:[EMAIL PROTECTED]

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Ajax.NET Professional" group.

To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]

For more options, visit this group at http://groups.google.com/group/ajaxpro

The latest downloads of Ajax.NET Professional can be found at 
http://www.ajaxpro.info
-~----------~----~----~----~------~----~------~--~---

Reply via email to