What for ?

In my opinion, I wrote this application for use behind the firewall:

1. For example, your office workstation is behind a very secure firewall. The only way that you can communicate from your home PC is through email or http. If the company has socks servers setup, then you can use remote port forward with ssh to establish a connection to your home IP address. Suppose you dial up to an ISP that gives you a dynamic IP address. The only way is to publish this IP address by email or put it on your own web page. Then set up your office workstation continuously detecting the new IP address and launch ssh to connect to your home PC.
2. If your organisation only allows email and http, and is without socks server to allow outgoing connections, then you can use this tool to gain some access but in a slow and inconvenient way.
3. Imagine your home PC is connected to the internet at all time and you hardly connect to your home PC from work. Instead, you can switch on or off all the listening services (such as ftp server, telnet server, etc) on your home PC with this application. For instance, you can send an actim event with a command ID, This active server recognises the ID and activates all the listening services. Then the user can telnet, ftp, ssh, etc to the home PC. When the user is finished, the user sends another actim event to switch off all the services. This is one way to protect your home PC. Of course, in this scenario, you must connect to your ISP mail server at all times.