$Id: BUGS,v 1.5 2000/03/30 07:00:10 shane Exp $

- Netscape has a timing bug when getting a directory list.  Getting a directory 
  works like this:

     o client designates port via PORT or PASV
     o server responds
     o client requests directory via LIST or NLST
     o server responds 
     o server opens data channel
     o server sends directory list over data channel
     o server closes data channel
     o server responds

  I *think* the problem is that the final response may get to the client 
  before the data channel close is recognized, possibly because of the
  way that threads work within Netscape.  This can be fixed by adding
  a delay after the close() before the server response, but that may
  not work well over the Internet.

  Note that the code currently sets the socket to linger on close until
  the other side has responded, and it shuts down the incoming data 
  channel on the socket as soon as it gets a connection, in an attempt
  to prevent this behavior.

- On Solaris, new POSIX threads cannot be created from a chroot() jail!
  It might be possible to use Solaris threads to create threads.  If not
  I'll probably just scrap Solaris.

