[proxyTools-announce] new localProxy windows executable - finally!

[wayne <wa...@ny...>]

The Windows executable version of localProxy has gone up to 
Sourceforge. Judging by the number of downloads of the last 
(April) binary, I expect a good market for this one :-)

Pick it up at:
http://prdownloads.sourceforge.net/proxytools/localProxyWinExe01-09-07.zip

I probably should add that the binaries are only for 
localProxy front and back ends, not for mergeHosts, nor any 
other proxy tools yet.

Let me hear some feedback please. Good or bad is ok.

It took a long time to make the binary, but now I have scripts etc. set up, 
I'll make new ones more easily.

-wayne


Release notes:

This file contains MS Windows executable (and full source, docs etc.).
I noticed a couple of minor problems after packaging this one:
1. warning message in the front-end log window each time the getStats, or 'show running config' buttons are pressed. I haven't been able to debug this yet.
2. On starting the backend, the GUI is meant to wait for the backend to start and then request the running configuration (to display the services, commStrats, layer 0 and 1 hosts etc.). This fails (quietly) in the Windows executable, and everything works normally except that the GUI windows are not filled in. A workaround is to click 'show running config' once the back end is ready to be used, and then click another config and back to yours.
Not very nice, but I didn't get to fix it in time.
3. The executable is unable to handle the code for non-blocking connects that makes the source version more responsive. I may be able to make this work yet, but it needs more time. he symptoms are that if you disconnect, localProxy will probably continue to timeout (30 secs per socket) on each request. Not pleasant.

Apart from these things, I think it's working well. Let me know.

Good luck.

wa...@ny...
http://proxytools.sourceforge.net
http://www.angelfire.com/my/6waynes


Change log:

1. Many changes since the package release earlier today to make the executable work (*very* painful stuff!).
These changes will go to CVS (I don't need to make a package - they were mostly just for the executable).

-wayne