Hi,
It is very normal for the DatePicker to make additional request to the server initially because DatePicker requires a number of JavaScript files to run. So when you intially load a page with DatePicker, it will try to load those JavaScript files. However once loaded, the browser should cache them and next time you should not see them to be loaded again.
If you see them to be loaded everytime, try to:
1. Check your browser's cache settings;
2. Turn on physical JavaScript files. See here for more details:
http://doc.essentialobjects.com/library/1/installationanddeployment/deploy.aspxThe Calendar also uses iframes and they require an empty document to work; In case you run over HTTPS, a separate non-empty document is needed (loaded from the server). None of these should be any of concern.
In any case, number of request alone is not an issue. For example, if you have a page with 10 images, then every time the page loads, you may see 10 requests to the server. However while the initial 10 requests will download all 10 images, subsequent requests will only check if the images have been changed (if the browser decides to check at all). In all cases you may see up to 10 requests, but the images are only downloaded once.
So please check whether it's just empty request, or request that pulls a lot of data from your server every time. As explained above, generally empty request alone is not a problem and we will not investigate. However if you see other unusual things (such as it is really excessive, causes other problem, or the Url that it requests for does not make sense, etc), do let us know and we will see what we can do.
Thanks