Hi,
Please check whether you are getting HTTP POST or HTTP GET. It is not normal to have that many times HTTP POSTs. However it is normal to have that many HTTP GETs. The reason is by default we use eo_web.ashx to render all our JavaScript files. So for example if we were to use three JavaScript files a.js, b.js and c.js, instead of seeing your browser making three requests (HTTP GETs) for a.js/b.js/c.js, you would see it making three requests to eo_web.ashx. Our eo_web.ashx is very similar to ASP.NET 2.0’s WebResource.axd.
Generally the number of the request alone is not a concern because modern browsers rarely close the connection right away after one request/response. It would keep the connection open and reuse the connection to send the next request to the server. For example, if you have a page using 5 gif images (which is very normal), you will see 5 HTTP GET requests to the server.
Further more, browser should cache the result of these requests. For example, even if your page uses 10 images, browser will only request each of them once. If you load the page again, the browser won’t request these pages from server again. The same goes with our JavaScript files.
With IIS 6 there is a small extra cost when the page goes eo_web.ahsx instead of going to the .js file directly because the former goes through ASP.NET pipe line and the later does not. If this concerns you, you can enable physical JavaScript file and it will no longer go through eo_web.ashx (look for physical JavaScript file):
http://doc.essentialobjects.com/library/1/installationanddeployment/deploy.aspxIf you see many HTTP POSTs then it is not normal. SpellChecker does send HTTP POST to the server to perform spell checking but it should not take 5 requests to do so. UpdatePanel’s HTTP POST should go back to the original page instead of eo_web.ashx.
Beside there is no caching for HTTP POST. So if you see 5 HTTP GETs, then most likely it only occurs when the page is first loaded. But if you see 5 HTTP POSTs, then most likely it will happen every time the page loads, which is obviously a lot worse. If that’s the case please try to create a test page/project that reproduce the problem and we will be happy to take a look to see what we can find.
Thanks!