/*                                                   W3C Reference Library libwww HTNet Class
                                      THE NET CLASS
                                             
 */
/*
**      (c) COPYRIGHT MIT 1995.
**      Please first read the full copyright statement in the file COPYRIGH.
*/
/*

   The Net class manages information related to a "thread" in libwww. As libwww threads
   are not really threads but a notion of using interleaved, non-blocking I/O for
   accessing data objects from the network (or local file system), they can be used on any
   platform with or without support for native threads. In the case where you have an
   application using real threads the Net class is simply a object maintaining links to
   all other objects involved in serving the request. If you are using the libwww pseudo
   threads then the Net object contains enough information to stop and start a request
   based on which BSD sockets are ready. In practise this is of course transparent to the
   application - this is just to explain the difference.
   
   When a Request object is passed to the Library , the core creates a new HTNet object pr
   channel used by the request. In many cases a request only uses a single channel object
   but for example FTP requests use at least two - one for the control connection and one
   for the data connection.
   
   You can find more information about the libwww pseudo thread model in the Multithread
   Specifications.
   
   This module is implemented by HTNet.c, and it is a part of the W3C Reference Library.
   
 */
#ifndef HTNET_H
#define HTNET_H
/*

   The HTNetobject is the core of the request queue management. This object contains
   information about the socket descriptor, the input read buffer etc. required to
   identify and service a request.
   
 */
typedef struct _HTNet HTNet;

#include "HTEvent.h"
#include "HTReq.h"
#include "HTTrans.h"
#include "HTHost.h"
#include "HTChannl.h"
#include "HTDNS.h"
/*

BEFORE AND AFTER FILTERS

   Filter functions can be registered to be called beforeand aftera request has either
   been started or has terminated. The following functions are the generic registration
   mechanisms where we use lists as the basic data container. Then there is two methods
   for binding a list of filter functions to the set which is called beforeand to the set
   set which is called after
   
   In both cases there can be more than one filter function which are called on turn and
   each filter function can be associated with a status code of the request. For example
   one filter function can be registered for HT_LOADED, another for HT_ERRORetc.
   
  Register a Net Filter
  
   Several filters can be registered in which case all of them are called in the reverse
   order of which they were registered (last one first). We name the calling mechansm of
   calling the filter for the beforeloop and the afterloop.
   
   In case the filter function is registered as being called afterthe request has
   terminated the result of the request is passed to the function. The status signifies
   which call back function to call depending of the result of the request. This can be
   
  HT_ERROR               An error occured
                         
  HT_LOADED              The document was loaded
                         
  HT_NO_DATA             OK, but no data
                         
  HT_NO_ACCESS           The request could not be succeeded due to lack of credentials
                         
  HT_NO_PROXY_ACCESS     The request could not be succeeded due to lack of credentials for
                         accessing an intermediate proxy
                         
  HT_RETRY               Retry request after at a later time
                         
  HT_PERM_REDIRECT       The request has been permanently redirected and we send back the
                         new URL
                         
  HT_TEMP_REDIRECT       The request has been temporaryly redirected and we send back the
                         new URL
                         
  HT_ALL                 All of above
                         
   Any filter can return any code it likes, but _IF NOT_ the code is HT_OK, then the
   filter loop is stopped. If we are in the beforeloop and a filter returns anything else
   than HT_OKthen we immediately jump to the afterloop _passing_ the last return code from
   the beforeloop.
   
 */
typedef int HTNetCallback (HTRequest * request, void * param, int status);

extern BOOL HTNetCall_add (HTList * list, HTNetCallback *cbf,
                          void * param, int status);
/*

  Delete a single Filter
  
   Removes a filter function from a list
   
 */
extern BOOL HTNetCall_delete (HTList * list, HTNetCallback *cbf);
/*

  Delete a list of Filters
  
   Unregisters all call back functions in the list
   
 */
extern BOOL HTNetCall_deleteAll (HTList * list);
/*

  Call List of Registered Filter Functions
  
   Call all the filters registered in the list _IF_ not the status is HT_IGNORE. The
   filters are called in the order of which they were registered. At the moment an
   application filter is called, it can free the request object - it is no longer used by
   the Library. Returns what the last filter returns
   
 */
extern int HTNetCall_execute (HTList * list, HTRequest * request, int status);
/*

  Handling BEFORE Filters
  
   Global set of filters BEFORE the request is issued. The list can be NULL.
   
 */
extern BOOL HTNetCall_addBefore (HTNetCallback *cbf, void * param, int status);
extern BOOL HTNetCall_deleteBefore (HTNetCallback * cbf);

extern BOOL HTNet_setBefore     (HTList * list);
extern HTList * HTNet_before    (void);

extern int HTNet_callBefore     (HTRequest *request, int status);
/*

  Handling AFTER Filters
  
   Global set of filters AFTER the request is issued. The list can be NULL
   
 */
extern BOOL HTNetCall_addAfter  (HTNetCallback *cbf, void * param, int status);
extern BOOL HTNetCall_deleteAfter (HTNetCallback * cbf);

extern BOOL HTNet_setAfter      (HTList * list);
extern HTList * HTNet_after     (void);

extern int HTNet_callAfter      (HTRequest *request, int status);
/*

SOCKET RESOURCE MANAGEMENT

   The request queue ensures that no more than a fixed number of TCP connections are open
   at the same time. If more requests are handed to the Library, they are put into the
   pending queue and initiated when sockets become free.
   
  Number of Simultanous open TCP connections
  
   Set the max number of simultanous sockets. The default value is HT_MAX_SOCKETS which is
   6. The number of persistent connections depend on this value as a deadlock can occur if
   all available sockets a persistent (see the DNS Manager for more information on setting
   the number of persistent connections). The number of persistent connections can never
   be more than the max number of sockets-2, so letting newmax=2 prevents persistent
   sockets.
   
 */
extern BOOL HTNet_setMaxSocket (int newmax);
extern int  HTNet_maxSocket (void);
/*

  Socket Counters
  
 */
extern void HTNet_increaseSocket (void);
extern void HTNet_decreaseSocket (void);

extern int HTNet_availableSockets (void);
/*

  Persistent Socket Counters
  
 */
extern void HTNet_increasePersistentSocket (void);
extern void HTNet_decreasePersistentSocket (void);

extern int HTNet_availablePersistentSockets (void);
/*

  Any Ongoing Connections?
  
   Returns whether there are active requests. Idle persistent sockets do not count as
   active.
   
 */
extern BOOL HTNet_isIdle (void);
/*

  List Active Queue
  
   Returns the list of active requests that are currently having an open connection.
   Returns list of HTNet objects or NULL if error.
   
 */
extern HTList *HTNet_activeQueue (void);
extern BOOL HTNet_idle (void);
/*

  Are we Active?
  
   We have some small functions that tell whether there are registered requests in the Net
   manager. There are tree queues: The active, the pending, and the persistent. The
   activequeue is the set of requests that are actively sending or receiving data. The
   pendingis the requests that we have registered but which are waiting for a free socket.
   The Persistentqueue are requets that are waiting to use the same socket in order to
   save network resoures (if the server understands persistent connections).
   
    Active Reqeusts?
    
   Returns whether there are requests in the activequeue or not
   
 */
extern BOOL HTNet_idle (void);
/*

    Registered Requests?
    
   Returns whether there are requests registered in any of the lists or not
   
 */
extern BOOL HTNet_isEmpty (void);
/*

  List Pending Queue
  
   Returns the list of pending requests that are waiting to become active. Returns list of
   HTNet objects or NULL if error
   
 */
extern HTList *HTNet_pendingQueue (void);
/*

CREATION AND DELETION METHODS

   The Net object is intended to live as long as the request is still active. In that
   regard it is very similar to the Request Object. However, the main difference is that a
   Net object represents a "thread" in the Library and a request may have multiple
   "threads" - an example is a FTP request which has a thread to handle the control
   connection and one to handle the data connections.
   
  Create a new Object
  
   If we have more than HTMaxActive connections already then put this into the pending
   queue, else start the request by calling the call back function registered with this
   access method. Returns YES if OK, else NO
   
 */
extern BOOL HTNet_newClient (HTRequest * request);
/*

   You can create a new HTNet object as a new request to be handled. If we have more than
   HTMaxActive connections already then return NO. Returns YES if OK, else NO
   
 */
extern BOOL HTNet_newServer (HTRequest * request, HTNet * net, char *access);
/*

   And you can create a plain new HTNet object using the following method:
   
 */
extern HTNet * HTNet_new (SOCKET sockfd, HTRequest * request);
/*

  Duplicate an existing Object
  
   Creates a new HTNet object as a duplicate of the same request. Returns YES if OK, else
   NO.
   
 */
extern HTNet * HTNet_dup (HTNet * src);
/*

  Launch a Net Object
  
   Start a Net obejct by calling the protocol module.
   
 */
extern BOOL HTNet_start (HTNet * net);
/*

  Delete an Object
  
   Deletes the HTNet object from the list of active requests and calls any registered call
   back functions IF not the status is HT_IGNORE. This is used if we have internal
   requests that the app doesn't know about. We also see if we have pending requests that
   can be started up now when we have a socket free. The filters are called in the reverse
   order of which they were registered (last one first);
   
 */
extern BOOL HTNet_delete (HTNet * me, int status);
/*

  Delete ALL HTNet Objects
  
   Deletes all HTNet object that might either be active or pending We DO NOT call the call
   back functions - A crude way of saying goodbye!
   
 */
extern BOOL HTNet_deleteAll (void);
/*

NET CLASS METHODS

  Make an Object Wait
  
   Let a net object wait for a persistent socket. It will be launched from the
   HTNet_delete() function when the socket gets free.
   
 */
extern BOOL HTNet_wait (HTNet *net);
/*

  Priority Management
  
   Each HTNet object is created with a priority which it inherits from the Request
   manager. However, in some stuations it is useful to be to change the current priority
   after the request has been started. These two functions allow you to do this. The
   effect will show up the first time (which might be imidiately) the socket blocks and
   control returns to the event loop. Also have a look at how you can do this before the
   request is issued in the request manager.
   
 */
extern HTPriority HTNet_priority (HTNet * net);
extern BOOL HTNet_setPriority (HTNet * net, HTPriority priority);
/*

  Persistent Connections
  
   You can set a Net object to handle persistent connections for example using HTTP, NNTP,
   or FTP. You can control whether a Net object supports persistent connections or not
   using this function.
   
 */
extern BOOL HTNet_persistent (HTNet * net);
/*

   You can set or disable a Net object supporting persistent connections using this
   function:
   
 */
extern BOOL HTNet_setPersistent (HTNet *           net,
                                 BOOL              persistent,
                                 HTTransportMode   mode);
/*

  Kill a Request
  
   Kill the request by calling the call back function with a request for closing the
   connection. Does not remove the object. This is done by HTNet_delete() function which
   is called by the load routine. Returns OK if success, NO on error
   
 */
extern BOOL HTNet_kill (HTNet * me);
/*

  Kill ALL requests
  
   Kills all registered (active+pending) requests by calling the call back function with a
   request for closing the connection. We do not remove the HTNet object as it is done by
   HTNet_delete(). Returns OK if success, NO on error
   
 */
extern BOOL HTNet_killAll (void);
/*

  Create Input and Output Streams
  
   You create the input stream and bind it to the channel using the following methods.
   Please read the description in the HTIOStream module on the parameters target, param,
   and mode. Both methods return YES if OK, else NO.
   
 */
extern HTInputStream * HTNet_getInput (HTNet * net, HTStream * target,
                                       void * param, int mode);

extern HTOutputStream * HTNet_getOutput (HTNet * net, void * param, int mode);
/*

  Net Context Descriptor
  
   Just like the request object, a net object can be assigned a context which keeps track
   of context dependent information. The Library does not use this information nor does it
   depend on it but it allows the application to customize a net object to specific uses.
   
 */
extern BOOL HTNet_setContext (HTNet * net, void * context);
extern void * HTNet_context (HTNet * net);
/*

  Socket Descriptor
  
 */
extern BOOL HTNet_setSocket (HTNet * net, SOCKET sockfd);
extern SOCKET HTNet_socket (HTNet * net);
/*

  The Request Object
  
   The Request object is normally set up automatically but can be changed at a later time.
   
 */
extern BOOL HTNet_setRequest (HTNet * net, HTRequest * request);
extern HTRequest * HTNet_request (HTNet * net);
/*

  The Transport Object
  
   The transport object is normally set up automatically but can be changed at a later
   time.
   
 */
extern BOOL HTNet_setTransport (HTNet * net, HTTransport * tp);
extern HTTransport * HTNet_transport (HTNet * net);
/*

  The Channel Object
  
 */
extern BOOL HTNet_setChannel (HTNet * net, HTChannel * channel);
extern HTChannel * HTNet_channel (HTNet * net);
/*

  The Host Object
  
 */
extern BOOL HTNet_setHost (HTNet * net, HTHost * host);
extern HTHost * HTNet_host (HTNet * net);
/*

  The DNS Object
  
   The DNS object keeps track of the DNS entries that we have already checked out.
   
 */
extern BOOL HTNet_setDns (HTNet * net, HTdns * dns);
extern HTdns * HTNet_dns (HTNet * net);
/*

   If we are talking to a multi-homed host then we may connect to any of the homes. In
   that case we store the current home in the Net object so that we can query about it
   later.
   
 */
extern int HTNet_home (HTNet * net);
/*

 */
#endif /* HTNET_H */
/*

   
   ___________________________________
   
                             @(#) $Id: HTNet.html,v 2.43 1996/08/19 18:30:50 frystyk Exp $
                                                                                          
    */
