Click here to Skip to main content
15,944,136 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
See more:

Here's what I understand how Jquery Ajax method call works with static web methods.

First the page object is created or server to serve the page when you try to load a webpage. But when you make an ajax call from Jquery ajax method you actually point to a static web method which cannot access any of the page controls as it cannot create an instance of the page in itself.

So can I put it this way - These static web methods cannot access the page's controls or their view state hence the danger of multiple requests and concurrency does not arise?

You call a static web method which means it does not have an associated object making it stateless(why do they use the term stateless?), which there by makes it work like a service which takes data, processes it, and returns something but does not keep anything to itself. Also you can choose to change the state of the controls present on the webpage by getting data in this manner and using JavaScript as there is no view state involved.

We can therefore presume that this workflow will not cause any concurrent access problems even though it uses static methods and fields.

Is there any flaw in my understanding?.
Updated 5-Nov-15 18:05pm

1 solution

It is probably better to post this kind of question here: ASP.NET Forum[^]
Share this answer

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900