[BACK]Return to WWWApp.html CVS log [TXT] [DIR] Up to [Public] / libwww / Library / src
File:  [Public] / libwww / Library / src / WWWApp.html
Revision 2.2: download - view: text, annotated - select for diffs
Tue Nov 14 23:30:29 1995 UTC (28 years, 7 months ago) by frystyk
Branches: MAIN
CVS tags: HEAD
Better interface for DLL

<HTML>
<HEAD>
<TITLE>Non-Mandatory Application Include File</TITLE>
<!-- Changed by: Henrik Frystyk Nielsen, 14-Nov-1995 -->
<NEXTID N="z11">
</HEAD>
<BODY>

<H1>Non-Mandatory Application Include File</H1>

<PRE>
/*
**	(c) COPYRIGHT MIT 1995.
**	Please first read the full copyright statement in the file COPYRIGH.
*/
</PRE>

In addition top the basic W3C Reference Library include file called <A
HREF="WWWLib.html">WWWLib.h</A> you <EM>can</EM> also include this
file called WWWApp.h depending on the needs of your
application. However, it is not required and none of the files
included below are ever used in the core part of the Library
itself. Only if this file is included, the extra modules will get
included in the linked object code. It is also possible to include
only a subset of the files below if the functionality you are after is
covered by them.

<PRE>
#ifndef WWWAPP_H
#define WWWAPP_H
</PRE>

<H2>Application Specific Library Includes</H2>

<PRE>
#ifdef __cplusplus
extern "C" { 
#endif
</PRE>

<H2>Initialization</H2>

The core parts of the Library is a framework for adding
functionailty. It has hooks for adding protocol modules, like for
example HTTP, FTP, and also for adding streams that can convert from
one media type to some other type, or presenting the result to the
user. In the distribution file of the Library you will find a large
set of porotocol modules and streams already implemented. However, in
order to use these you need to initialize them. This can be done by
using the files in the <A HREF="HTInit.html">HTInit</A> module. You
can modify this module as you like to fit your particular needs.

<PRE>
#include "<A HREF="HTInit.html">HTInit.h</A>"
</PRE>

<H2>Generating the First Anchor</H2>

This module provides some "make life easier" functions in order to get
the application going. They help you generate the first anchor, also
called the <EM>home anchor</EM>. It also contains a nice set of
default WWW addresses.

<PRE>
#include "<A HREF="HTHome.html">HTHome.h</A>"
</PRE>

<H2>Logging</H2>

Often it is required to log the requests issued to the Library. This
can either be the case if the application is a server or it can also
be useful in a client application. This module provides a simple
logging mechanism which can be enabled if needed.

<PRE>
#include "<A HREF="HTLog.html">HTLog.h</A>"
</PRE>

<H2>History Management</H2>

Another type of logging is keeping track of which documents a user has
visited when browsing along on the Web. The Library history manager
provides a basic set of functionality to keep track of a linear
history list.

<PRE>
#include "<A HREF="HTHist.html">HTHist.h</A>"
</PRE>

<H2>Rule File Management</H2>

Another way to initialize applications is to use a rule file, also
known as a configuration file. This is for example the case with the
W3C httpd and the W3C Line Mode Browser. This module provides basic
support for configuration file management and the application can use
this is desired. The module is not referred to by the Library.

<PRE>
#include "<A HREF="HTRules.html">HTRules.h</A>"
</PRE>


End of application specific modules

<PRE>
#ifdef __cplusplus
} /* end extern C definitions */
#endif

#endif
</PRE>

End of WWWAPP definition

</BODY>
</HTML>
Webmaster