2) InstantUpdate clientWhen I have built my own client to be released, the InstantUpdate.exe is just copied to output folder. When it's running, it's trying to reach 163.242.55.191:3128, 163.242.55.192:3128, 163.242.55.193:3128 and not only my IP address with updates, but why? What kind of data it is sending to these 163.242.55.19x:3128 addresses? Is it possible to reduce data traffic to "not my" IPs?
I'm not sure what those IPs are. They aren't wyDay.com, and the Client isn't programmed to access anything outside of wyDay.com and whatever update/server file mirrors you specify.
I did a trace on those IPs, but it fails before it reaches the destination. But if I were to guess the cause for those IPs, I'd say it has something to do with your proxy settings.
As I mentioned above, the one file accessed on wyDay.com is to check for updates to the InstantUpdate Client. This will be customizable in the next version (coming in late June / early July). The Client source code will also be released so you'll be able to see that the "163.242.55.19x:3128" addresses are nowhere in the source.
1) Proxy:It is good to take proxy settings from Internet Explorer, but if I'm connected to my private net (with no proxy) and I will forget to switch off this proxy within the IE browser, the InstantUpdate will not connect at all. Is it possible to skip proxy settings in this case and use direct connection?
It is possible to override the default IE proxy settings, but I need a little more information on how you're using the Client on your local network. Would a command line switch suit you? That is, would something like this work for you?
InstantUpdate.exe /proxy:none
or
InstantUpdate.exe /proxy:"127.0.0.1:85"