[Psi-Devel] Feature Request: Proxy management
Stefan
psi_07 at green-sparklet.de
Sun Mar 9 05:31:29 PDT 2008
> in order to migrate Psi from one network
> to another, I have to:
>
Yes I know this too. I also have to do one mouse click more: I have to
set another port to connect to (if I use proxies, I have to use 443, if
I connect directly I have to use 5223).
If I go to another network, everything is set automatically: network
card configuration, VPN starts up (if necessary) and connects, browser
proxies are set, my standard printer changes to one aviable in this
network, ... all automatically, only Psi doesn't allow me to automatize
the proxy change.
I tried this some time ago, but I didn't find a proper solution to shut
down Psi through the command line. I had a small tool called "kill.exe"
but Psi didn't even notice that this tool wants it to exit. I had to use
the "force" option, but that caused to abort the Psi task so that all
unsafed changes would be lost - and I didn't want to do that.
Here are three options that I would like to see one of them in Psi:
* Let me specify a file for automatic proxy configuration as every good
webbrowser has it (http://en.wikipedia.org/wiki/Proxy_auto-config) and a
command line option to inform Psi that this file has changed (or Psi
automatically watches this file for changes if it can't connect).
* Give me a possibillity to change the proxies through the commandline.
* Give me a possibillity to properly shut down Psi through commandline
so that I can edit the configuration file with other tools, and restart
Psi again
All this is spoken for Windows systems :)
More information about the Psi-Devel
mailing list