* More testing
 * Write all the missing t/*.t test scripts

 * Simplify the LWP::Request handlers and callbacks.
 * Complete LWP5 compatibility modules: LWP::UserAgent and LWP::Simple
   Perhaps make a separate distribution for them until LWP5 can be
   declared obsolete.  'LWP5emu'
 * Finish the authentication hooks (digest especially)
 * LWP::Conn::HTTP improvements
     - bundling of multiple request in a single syswrite() when
       pipelining is likely to improve performance.
     - non-blocking gethostbyname (Net::DNS?)
     - minimize headers sent for second and following requests.
     - know something about idempotent methods
     - always pass response data through sinks (?)
     - support HTTP/1.0 Keep-Alive (?) (make more sense for a server)
     - try to record HTTP version number supported by the server
       in the LWP::Server object (or URI::Attr).
 * Make a single request able to override persistent connection
   behaviour (make a request always processed on its own connection)
 * LWP::Conn::FILE could support PUT and Content-Ranges
 * Other LWP::Conn implementations: FTP, NNTP, Gopher, MAILTO
 * Support HTTPS, TLS.  This might need restructuring of the LWP::Conn:HTTP.
   Perhaps the socket should be a member and not the HTTP connection object
   itself?
 * gzip/compress sinks
 * deflate parameters, find out if it matters...
 * tuning - make things go faster
 * documentation - as always

 * Caching support
 * Some applications (at least in order to gain some experience with
   using this interface).
 * Delayed spooling (for robots)
 * RobotUA

 * Move to same eventloop as Tk uses.  There appears to be a problem because
   the Tk fileevent does not allow a socket to be both readable and writable
   at the same time.  Grahams Event.pm does not work with current IO modules
   so I have not tried to use it yet.  Compatibility with Win32 is also a
   concern in all of this.


-------
$Id: Todo,v 1.12 1998/04/24 08:32:45 aas Exp $