/*    					W3C Sample Code Library libwww Core Interface!  Declaration of W3C Sample Code Library Core Interface!*//***	(c) COPYRIGHT MIT 1995.**	Please first read the full copyright statement in the file COPYRIGH.*//*This is the basic include file for the core of the W3C Sample Code Library.The core part of the Library is designed as a set of registration moduleswith no real functionality in itself. Instead all the functionality comeswhen the application registeres the modules that provides a desired functionaly,for example accessing HTTP servers or the local file system. The Libraryhas a special include file called WWWApp.h whichcontains all converters, protocol modules, and a lot of other "sugar" modulesthat can make the core a very powerful Web interface. You can include thisone if the application is to use all the functionality of the Library.*/#ifndef WWWCORE_H#define WWWCORE_H/**/#ifdef __cplusplusextern "C" { #endif/*(  System dependencies)The wwwsys.h file includes system-specific includefiles and flags for I/O to network and disk. The only reason for this fileis that the Internet world is more complicated than Posix and ANSI.*/#include "wwwsys.h"/*(  Generic Libwww Information)This module contains some generic functions for getting the name and versionof libwww. It also contains some global configuration options like if youcan access the local file system, for example.*/#include "HTLib.h"/*(  The Request Class)Libwww is based on a request/response paradigm and the Request class defines"an operation to be performed on a URL". The request object is themain entry point for an application to issue a request to the Library - alloperations on a URL must use a Request object.*/#include "HTReq.h"/*(  Request Methods)This module defines the set of methods that you can perform on a request,for example GET, HEAD, PUT, POST, DELETE,etc.*/#include "HTMethod.h"/*(  The Anchor (URL) Class)An anchor represents a region of a hypertextdocument which is linked to another anchor in the same or a different document.Another name for anchors would be URLs as an anchor represents all we knowabout a URL - including where it points to and who points to it.*/#include "HTAnchor.h"/*(  The Link Class)A Link represents the link between anchor objects.By keeping the link as a object and not as part of the anchor we are capableof handling link semantics in a much more organized way. For example, wecan then search for link types among all the link objects that we have created.*/#include "HTLink.h"/*(  Parsing URLs)This module contains code to parse URIs for the various components accordingto the URI syntax*/#include "HTParse.h"/*(  Escaping and Unescaping URLs)URLs are written only with the graphic printable characters of the US-ASCIIcoded character set. All other characters must be escaped before they canbe used in URLs. This module defines the methods required for escaping andunescaping the URLs.*/#include "HTEscape.h"/*(  URL Trees and Hierarchies)A URL tree is a data class that can store allthe information we know about a URL hierarchy. Typically, a URL hierarchyis what a client sees of a Web server but it can also be the view a serverhas of itself. A URL tree has the advantage that it can be searched usingURLs or using realms. The letter is most useful to "guess" informationabout a remote URL that we haven't seen before.*/#include "HTUTree.h"/*(  Web Related String Functions)This module is like the generic string utilitymodule but it contains more Web related string utility functions. Examplesare functions that return a date string, a Message ID stringetc.*/#include "HTWWWStr.h"/*(  The User Profile Class)The User profile class manages what we know about a user on thishost. This can for example be the FQDN of the host, the user's emailaddress, the time zone, the news server etc.*/#include "HTUser.h"/*(  The Event Class)The Event Class defines any event manager to be used by libwww for handlingevents.*/#include "HTEvent.h"/*(  The Network Trace Handler)The Network Trace Handler provides an easy mechanismfor tracing memory problems. It gives a complete dump of all read and writteninformation to and from the network*/#include "HTMemLog.h"/*(  The Error Class)The Error class provides an easy API for registeringerrors ocurring while the Library serves a request. All errors are registeredin an "error stack" in the Request object whichallows for nested errors.*/#include "HTError.h"/*(  The Alert Class)The Alert class defines a set of methods to beused by libwww to be used for passing prompts and message to a user.*/#include "HTAlert.h"/*(  The Format Manager)The Format Manager is responsible for setting up the stream pipe from theChannel Object to the RequestObject when data is arriving, for example as a response to sHTTP Get request. The Format Manager is alsoresponsible for keeping track of the "preferences" of the applicationand/or user. It is an integral part of the Web and HTTP, that the clientapplication can express its preferences as a set of "accept" headers in aHTTP request.*/#include "HTFormat.h"/*(  The Generic Stream Class)The Stream class defines objects which acceptsa sequence of characters. Streams may also have an output in which case multiplestream objects can be cascaded to build a stream pipe where the output ofa stream is directed into the input of the next stream object "down the line".*/#include "HTStream.h"/*(  The Structured Stream Class)The Structured stream class defines objects whichaccepts a structured sequence of characters for eaxmple a SGML document.I'll rephrase that. A structured object is am ordered tree-structured arrangementof data which is representable as text. An example is theSGML parser which outputs to a Structured Object.*/#include "HTStruct.h"/*(  No Free Stream)This stream is a throughline for all methods except FREE andABORT. This means that it can be use to put ahead of streams that youdon't want to be freed or aborted until you are redy to do ityourself.*/#include "HTNoFree.h"/*(  The Input/output Stream Classes)The I/O Stream class defines objects whichaccepts a sequence of characters to and from atransport*/#include "HTIOStream.h"/*(  The DNS Class)The DNS Class defines generic access to  the DNS system. It maintainsa cache of all visited hosts so that subsequent connects to the same hostdoesn't imply a new request to the DNS every time.*/#include "HTDNS.h"/*(  The Host Class)The Host class manages what we know about a remotehost. This can for example be what type of host it is, and what version itis using.*/#include "HTHost.h"/*(  The Net Class)The Net class manages information related to a "thread"in libwww. As libwww threads are not really threads but a notion of usinginterleaved, non-blocking I/O for accessing data objects from the network(or local file system), they can be used on any platform with or withoutsupport for native threads.*/#include "HTNet.h"/*(  Internet Functions)This module has the common code for handling typical Internet functions likegetting the name of the local host, getting the domain name and email addressof user etc.*/#include "HTInet.h"/*(  The Transport Class)The Transport Class defines a transport as used by theHTChannel class to communicate with the network,the local file system etc. New transport objects may be registered at anytime. This allows the application to easily hook in its own transport layers.*/#include "HTTrans.h"/*(  The Protocol Class)The Protocol class defines an application level protocol (HTTP, FTP, Gopher,etc.) to be used by libwww. Please note that access to the local file systemalso is considered to be an appliaction level protocol treated identicallyto for example the HTTP protocol.*/#include "HTProt.h"/*End of Core modules*/#ifdef __cplusplus} /* end extern C definitions */#endif#endif/*    @(#) $Id: WWWCore.html,v 2.21 1999/02/07 18:31:24 frystyk Exp $*/