/*    					W3C Sample Code Library libwww Default Initialization!  Application 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 set of default functions, for example foraccessing HTTP and FTP servers, parsingRFC822 headers etc. but it must all be registered by the application beforethe core knows about it. You can either register the parts directly throughthe many initialization functions in the Initialization Interface or youcan use these "precompiled" profiles which are set up to contain the featuersoften used by the a specific type of application, for example a client, aserver, a robot etc.This module helps the application programmer setting up all this functionality,but it is important to note that none of it is required in order touse the Library. All the profiles declared below superseed the Library coreinitialization function HTLibInit() which is defined in theHTLib module.This module is implemented by HTProfil.c, and itis a part of the W3C Sample CodeLibrary. You can also have a look at the otherInitialization modules.*/#ifndef HTPROF_H#define HTPROF_H#include "WWWLib.h"#include "WWWInit.h"/*.  Client Application Profiles.We have a couple of different client application profiles suited to differenttypes of clients.(  Traditional Client Application)The first uses a non-blocking socket interface which enables the applicationto perform multiple requests simultanously - in everyday words calledpseudo-threads. Besides that this profile contains typical filters for handlingredirection, authentication, logging, and proxy servers.*/extern void HTProfile_newClient (	const char * AppName,	const char * AppVersion);/*(  Simple HTML Client)As above but furthermore contains the default libwwwHTML parser*/extern void HTProfile_newHTMLClient (	const char * AppName,	const char * AppVersion);/*(  Client without a Persistent Cache)This is the same as above except that it doesn't start the persistent cache.*/extern void HTProfile_newNoCacheClient (	const char * AppName,	const char * AppVersion);/*(  Simple HTML Client without Persistent Cache)As above but furthermore contains the default libwwwHTML parser*/extern void HTProfile_newHTMLNoCacheClient (	const char * AppName,	const char * AppVersion);/*(  Preemptive (Blocking) Client)Do not use preemptive profiles if you are doing PUT orPOST requests.We also have a blocking (preemptive) version of the same client interface.The difference is that this version uses traditional blocking sockets andhence only one request can be performed at the same time.*/extern void HTProfile_newPreemptiveClient (	const char * AppName,	const char * AppVersion);/*.  Robot Application Profile.The robot profile contains much of the same functionality as the client,but it does contain less filters. For example, robots are normally not interestedin performing automatic redirections or access authentication, and hencethis is not part of the robot profile.*/extern void HTProfile_newRobot (	const char * AppName,	const char * AppVersion);/*Do not use preemptive profiles if you are doing PUT orPOST requests.As for the client interfacem we also have a blocking (preemptive) versionof the same interface. The difference is that this version uses traditionalblocking sockets and hence only one reques can be performed at the same time.*/extern void HTProfile_newPreemptiveRobot (	const char * AppName,	const char * AppVersion);/*.  Delete a Profile.This is a generic profile cleanup that should be used on all the profilesabove. This will clean up the memory allocated by the profile and by theLibrary core itself. After calling this you can not call any Library functionagain. This call also supersedes the termination function for the Librarycore, HTLibTerminate() so that you don't have to call that aftercalling this function.*/extern void HTProfile_delete (void);/**/#endif/*    @(#) $Id: HTProfil.html,v 2.8 2000/07/12 10:44:41 kahan Exp $*/