/*    					W3C Sample Code Library libwww Default Initialization!  Default Initialization Modules and Profiles!*//***	(c) COPYRIGHT MIT 1995.**	Please first read the full copyright statement in the file COPYRIGH.*//*As mentioned in the Library Architecture,libwww consists of a small core and a large set of hooks for addingfunctionality. By itself, the core it not capable of performing any Web relatedtasks like accessing a HTTP server or parsing a HTML document. All thisfunctionality must be registered by the application. This way, the core oflibwww is kept application independent and can be used as the basic buildingblock for any kind of Web application. The Library comes with a large setof default functions, for example for accessing HTTP and FTP servers, parsingMIME headers etc. This module helps the application programmer setting upall this functionality, but it is important to note that none of it isrequired in order to use libwww.*/#ifndef WWWINIT_H#define WWWINIT_H/**/#ifdef __cplusplusextern "C" { #endif/*.  Default Protocols, Transports, MIME Headers, Dialogs etc..This module contains a large set of default initialization functions forprotocol modules, stream converters, event managers etc.*/#include "HTInit.h"/*.  Application Profiles.Application profiles are initialization functions that are "preset" to initializethe Library with the set of features often used in clients,servers, robots, and proxy servers. They are basicallycollections of the more detailed initialization functions that you can findlater in this interface description. In many cases you do not need to useanything else than the profiles, but if you have more specific requirementsthen you can always fall back on using the initialization functions belowor even werite your own extensions.*/#include "HTProfil.h"/**/#ifdef __cplusplus} /* end extern C definitions */#endif#endif/*    @(#) $Id: WWWInit.html,v 2.11 1999/03/30 22:31:58 frystyk Exp $*/