/Tags/ASPNET/RSS en http://labs.ecraft.com/Content/icons/favicon.png /Tags/ASPNET/RSS 64 64 Tim Viney I love this, great blog, thanks. I'm developing an on going asp.net app that is growing arms and legs. One major page has about 10 user controls each in it's own update panel. There is a heck of alot of text in gridviews and datalists all over the page, so as you can imagine it can be a tad slugish. I'm working on a part where I need to check that a corisponding file exists on the server when a user clicks a checkbox in a large datalist. To do this check in an update panel and wate for the big roundtrip would be unexceptable I think, but could be just the ticket for my scenario I think :) Thanks, very usefull. http://labs.ecraft.com/Code/Calling-web-services-from-JavaScript-with-ASPNET-AJAX-Answering-the-Why-and-How-questions#c-201003251024395 http://labs.ecraft.com/Code/Calling-web-services-from-JavaScript-with-ASPNET-AJAX-Answering-the-Why-and-How-questions#c-201003251024395 Thu, 25 Mar 2010 22:24:39 GMT per.lundberg@ecraft.com Thanks for the comment, Robin. You're right (even though you're expressing yourself slightly incorrectly - it's the ethernet frame size, not the TCP/IP packet, that is normally limited to 1,5 kbytes - 1514 bytes including 14 bytes or so worth of header). But then again, TCP/IP packets are normally delivered in ethernet frames, so my 20 KiB TCP/IP packet is likely to be split by the TCP/IP layer in my Windows Vista into suitable ethernet frames anyway, so in practice what you say is true, even it's theoretically incorrect. ;-) Anyway, in my example both messages will be delivered in 1 ethernet frame, so the difference is 0% in terms of packets being sent over the wire. Still, the overhead has to be processed by the target TCP/IP layer and so forth. In real-world scenarios though, my reasoning might be more correct (even though the 97,9% performance increase is unlikely to remain :-) ). It would be interesting to see some figures of more complex scenarios of UpdatePanel vs "raw" Javascript. I think usually people who make more complex stuff usually prefer the UpdatePanel approach though, since it makes the solution more homogeneous (all the code in simple C# code-behind files rather than some parts in Javascript files hidden away somewhere...). http://labs.ecraft.com/Code/Calling-web-services-from-JavaScript-with-ASPNET-AJAX-Answering-the-Why-and-How-questions#c-201001220840221 http://labs.ecraft.com/Code/Calling-web-services-from-JavaScript-with-ASPNET-AJAX-Answering-the-Why-and-How-questions#c-201001220840221 Fri, 22 Jan 2010 08:40:22 GMT Robin Lauren Your intentions are good but your reasoning is flaky. As long as a return packet is under 1.5 kB, it doesn't really matter how small it is since it's still going to fit inside one TCP/IP pcket. I'm not a C# coder so i can't comment on the code purity issues, but i much appreciate the cleaner return value of "just the facts, mam". http://labs.ecraft.com/Code/Calling-web-services-from-JavaScript-with-ASPNET-AJAX-Answering-the-Why-and-How-questions#c-201001150117293 http://labs.ecraft.com/Code/Calling-web-services-from-JavaScript-with-ASPNET-AJAX-Answering-the-Why-and-How-questions#c-201001150117293 Fri, 15 Jan 2010 13:17:29 GMT