Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error
Strange issue with ASP .NET AJAX 1.0
Options
Previous Topic Next Topic
samsi
#1 Posted : Monday, August 3, 2009 9:32:56 PM(UTC)
Groups: Member
Joined: 8/3/2009(UTC)
Posts: 3
Location: india
Running into a strange issue.

My intranet app uses ASP .NET AJAX 1.0 extensively. Assuming the server is hosted internally at - http://192.168.155.3 - at port 80 ...

- When I access the web app from that very machine - using http://localhost - the app runs brilliantly - great response times, no problems with AJAX.

- When I access the web app from another machine in the intranet - using - http://192.168.153.3/ - response times are not as good, performance becomes inconsistent, its fast sometimes, sluggish sometimes, sometimes ajax calls timeout.

- When I access the web app from another machine, with proxy enabled - calling http://192.168.153.3 renders the website - performance being a little sluggish, but the real problem is that most of the ajax calls fail in this scenario. Say for eg. clicking on a gridview is supposed to populate a detailsview (ajax call) - such partial postbacks never complete, so the app becomes unusable with proxy on (even though the app is accessible, ajax stops working)

Any clarification and guidance would help.

Thanks.
Back to top
 |  Edit by user
Ultidev Team
#2 Posted : Tuesday, August 4, 2009 6:10:38 AM(UTC)
Ultidev Team

Groups: Administration
Joined: 11/3/2005(UTC)
Posts: 2,253

Thanks: 28 times
Was thanked: 60 time(s) in 59 post(s)
Hi there!

The system may become sluggish because current version of Cassini does not generate caching & conditional GET HTTP headers properly on the responses that serve JavaScript files. This may lead to the situation that over slow and proxied connections all the JS scripts are loaded completely from the server for each page. To get better view at what going on please consider intalling Fiddler - a great HTTP tracer - on the client machine and watch your requests and responses goign across the wire and see which ones fail.

If our guess is correct, then should be able to implement a relatively simply work-around with a little-bit of coding.

Please let us know if this infromation has helped.

Best regards,
UltiDev Team.
Please donate at http://www.ultidev.com/products/Donate.aspx to help us improve our products.
Back to top
WWW
Rss Feed  Atom Feed
Users browsing this topic
Guest (2)
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You can vote in polls in this forum.

Powered by YAF 1.9.5.5 | YAF © 2003-2011, Yet Another Forum.NET