Future developments

Blogs that update you on current affairs are very useful. After a good read, go to www.casinorating.com.au for fun casino games.

nzher-31tomlinsonAdditional:

Persons can tell the developer, which are considered to be important. So far there have not been feature requests [Sept-2003]:

Bug fixes and new configuration options. Persons maybe have to write. There could be more bugs than any user would possibly want.
A readline in loop, at the client end, allowing reconfiguring of the ‘track’ connections without any closing of the 2 main threads.
Port number blocking in the server. It is missing since I had not written code to read in a file from “./”
FTP support. Possibly I would use Juniper code may be the best option. (The general problem is that the FTP client discloses its own IP number through the proxy, and then FTP server connects back to the client instead of the proxy. The server proxy does not get the connection, and anyway, it lacks code lacks code to handle any returning FTP connection.)
Muxing over a single port 443 https thread. Getting unidirectional data over HTTP/1.1 ought be running first since encryption is a minor thing to the webserver, which would use the same CGI code whether I/O is encrypted or not.
Muxing over a large number threads. That could permit fast gaming in Europe.
Supprot for authentication and/or the Socks protocol of NEC.
The software might be put into a plug-in and provide multiplexing to some other program.

I am withholding the source code. There is possibility that proxy will be crippled so that it does not proxy violent fight-persons’ games in China.

A lot of the Ada code of the proxy is actually already online, here: http://ijs.co.nz/code/. The multiplexing and CGI code is withheld. There is some Ada code to parse incoming HTTP/1.0 headers.

Here is a sample *BSD/Linux script “xt” that an xterm window that resembles Windows 2000’s CMD.EXE’s:

S=”xterm -tn xterm-color -fg white -bg rgb:0/04/11 -b 5 -s -sl 9999 \
-sb -rightbar -si -sk -geometry 90×140 -title \$:`pwd` $@”
echo $S
exec $S

There are alternative options that wrap TCP in HTTP. They don’t multiplex, so they can leave more evidence behind. E.g. 18 log file lines for each download of a POP3 e-mail message.