Replying to a message of Brady Flowers to David Calafrancesco:
 BF> Replying to a message of David Calafrancesco to Brady Flowers:
 DC>> I have need of a socks/proxy aware telnet client. Can TE2/TE2pro
 DC>> handle that right now? If not is it a planned or possible direction
 DC>> to head in the future? More and more systems are going to be behind
 DC>> firewalls in the future and we should start getting a jump on the
 DC>> tools necessary to exist inside. 
 BF> This is definately something that will be addressed in TE/2 and TE/2
 BF> Pro sooner rather than later!
Okay, after a little research I find that, if you are running Warp 4 
Merlin),
then all of our TCP/IP based stuff that uses the IBM TCP/IP stack should
work just fine as-is in a socks/proxy situation.  This includes TE/2, TE/2 
Pro,
VT32, and JTelnet.  If you are running Warp 3 or SMP, then there are things
that the application developer has to do.  If you are using TE/2 or TE/2 Pro
with either the TCP/IP module for FTP Software's stack or Novell's stack, 
hen
things get quite difficult from the developer's point of view.
So, the bottom line is: If you're running Warp 4, there's nothing further to
do.  If you (or anyone reading this) need socks support on Warp 3, let me
know and I'll see what I can do.
PS: A note about JTelnet -- since this is a Java thing, it will be dependant
on how socket/socks support is handled on each platform it's run on.  Warp 4
should, again, be fine but I can't vouch (right now) for any other OS.
  -- Brady
--- FleetStreet 1.18+
---------------