Currently, the SessionServer listens on a
administrator-defined port for connections from the
TN3270 Emulator applet. This breaks in any environment
where the client may be behind a firewall. It also
requires the host to listen on the specified port,
creating a potential security hole.
For the first new release (0.2) (not the cleanup
initial release(0.1)), I think this is the most
important feature to add.
The general idea is to let the SessionServer servlet
accept connections wrapped in HTTP headers through an
HTTP Post. This will solve most (if not all) client
firewall problems, and presents no additional security
issues on the web host.
Moreover, this allows for front-end web servers talking
to an out-of-process JVM to forward the requests
appropriately. (e.g. Apache talking to Tomcat)
I've seen a couple of articles on doing this sort of
thing with servlets, but if anyone has any ideas, I'm
all ears. : )