G
Guest
Hi,
I have to create a web page in .net 1.1 having controls whose actions are
performed through AJAX, means user can do operation without any post back. In
back end I defined a Ajax method which is called every time whenever a hit is
made.
This method invokes a web method resides in Web Service. However I've some
confusion in which one is better:
1. Make Asynchronous call through web service and in callback access its
result.
2. Create an independent thread for every call and assign a method to this
thread and access result after the completion of thread.
However I experimented on both of the approaches and found some conclusions
on it.
a) Making Async calls through web service may cause some threads to loose
their callbacks they donot reach to their callback methods, specially when
web service is performing heavy operation.
b) Transport exception is common.
c) Using an individual thread for every operation might cause session vars
to loose their values. If user makes a hit for a Ajax method concurrently 30
or more times and the method is updation values in session.
d) DO NOT know how many maximum number of threads I can open in ASP.NET
application. Hope their must be some limitation. Although I succeded upto 80
threads...
Please suggest...
Abhishek
I have to create a web page in .net 1.1 having controls whose actions are
performed through AJAX, means user can do operation without any post back. In
back end I defined a Ajax method which is called every time whenever a hit is
made.
This method invokes a web method resides in Web Service. However I've some
confusion in which one is better:
1. Make Asynchronous call through web service and in callback access its
result.
2. Create an independent thread for every call and assign a method to this
thread and access result after the completion of thread.
However I experimented on both of the approaches and found some conclusions
on it.
a) Making Async calls through web service may cause some threads to loose
their callbacks they donot reach to their callback methods, specially when
web service is performing heavy operation.
b) Transport exception is common.
c) Using an individual thread for every operation might cause session vars
to loose their values. If user makes a hit for a Ajax method concurrently 30
or more times and the method is updation values in session.
d) DO NOT know how many maximum number of threads I can open in ASP.NET
application. Hope their must be some limitation. Although I succeded upto 80
threads...
Please suggest...
Abhishek