Annotation of libwww/Library/src/WWWApp.html, revision 2.13
2.1 frystyk 1: <HTML>
2: <HEAD>
2.12 eric 3: <!-- Changed by: Henrik Frystyk Nielsen, 16-Apr-1996 -->
4: <NEXTID N="z11">
2.13 ! frystyk 5: <TITLE>W3C Reference Library libwww Application Layer</TITLE>
2.1 frystyk 6: </HEAD>
7: <BODY>
2.12 eric 8: <H1>
9: Non-Mandatory Application Include File
10: </H1>
2.1 frystyk 11: <PRE>
12: /*
13: ** (c) COPYRIGHT MIT 1995.
14: ** Please first read the full copyright statement in the file COPYRIGH.
15: */
16: </PRE>
2.12 eric 17: <P>
18: In addition top the basic W3C Reference Library include file called
19: <A HREF="WWWLib.html">WWWLib.h</A> you <EM>can</EM> also include this file
20: called WWWApp.h depending on the needs of your application. However, it is
21: not required and none of the files included below are ever used in the core
22: part of the Library itself. Only if this file is included, the extra modules
23: will get included in the linked object code. It is also possible to include
24: only a subset of the files below if the functionality you are after is covered
25: by them.
2.1 frystyk 26: <PRE>
27: #ifndef WWWAPP_H
28: #define WWWAPP_H
29: </PRE>
30: <PRE>
31: #ifdef __cplusplus
32: extern "C" {
33: #endif
34: </PRE>
2.12 eric 35: <H2>
36: System dependencies
37: </H2>
38: <P>
2.11 frystyk 39: The <A HREF="sysdep.html">sysdep.h</A> file includes system-specific include
2.12 eric 40: files and flags for I/O to network and disk. The only reason for this file
41: is that the Internet world is more complicated than Posix and ANSI.
2.11 frystyk 42: <PRE>
43: #include "sysdep.h"
44: </PRE>
2.12 eric 45: <H2>
2.13 ! frystyk 46: Event Manager
! 47: </H2>
! 48: <P>
! 49: The core part of libwww only provides the hooks for the event manager. There
! 50: is no event loop internal to the core part. Instead the application must
! 51: provide the event loop in order to use either pseudo threads or real threads.
! 52: If the application only uses blocking sockets without threads then it is
! 53: not required to register any event loop at all. We provide a default
! 54: implementation of an event loop which you can either take or get some ideas
! 55: from.
! 56: <PRE>#include "<A HREF="HTEvntrg.html">HTEvntrg.h</A>"
! 57: </PRE>
! 58: <H2>
2.12 eric 59: Generating the First Anchor
60: </H2>
61: <P>
62: This module provides some "make life easier" functions in order to get the
63: application going. They help you generate the first anchor, also called the
64: <EM>home anchor</EM>. It also contains a nice set of default WWW addresses.
2.2 frystyk 65: <PRE>
66: #include "<A HREF="HTHome.html">HTHome.h</A>"
2.1 frystyk 67: </PRE>
2.12 eric 68: <H2>
69: User Dialogs and Messages
70: </H2>
71: <P>
72: You can register a set of callback functions to handle user prompting, error
73: messages, confimations etc. Here we give a set of functions that can be used
74: on almost anu thinkable platform. If you want to provide your own platform
75: dependent implementation then fine :-)
2.8 frystyk 76: <PRE>
77: #include "<A HREF="HTDialog.html">HTDialog.h</A>"
78: </PRE>
2.12 eric 79: <H2>
80: After Terminating a Request
81: </H2>
82: <P>
83: When a request is terminated, the application often has to do some action
84: as a result of the request (and of the result of the request). The Application
85: part of the Library provides two following modules to handle <EM>logging</EM>
86: and <EM>history management</EM>. You can register a <EM>POST request
87: handler</EM> in the <A HREF="HTNet.html">Net Manager</A> as described in
88: the <A HREF="../User/Using/Overview.html">User's Guide</A>.
89: <P>
90: You can find a function called <CODE>HTLoadTerminate</CODE> in the
91: <A HREF="HTHome.html">HTHome module</A> that enables all the functionality
2.4 frystyk 92: for handling a request result.
2.12 eric 93: <H3>
94: Logging
95: </H3>
96: <P>
97: Often it is required to log the requests issued to the Library. This can
98: either be the case if the application is a server or it can also be useful
99: in a client application. This module provides a simple logging mechanism
100: which can be enabled if needed.
2.1 frystyk 101: <PRE>
2.2 frystyk 102: #include "<A HREF="HTLog.html">HTLog.h</A>"
2.1 frystyk 103: </PRE>
2.12 eric 104: <H3>
105: History Management
106: </H3>
107: <P>
108: Another type of logging is keeping track of which documents a user has visited
109: when browsing along on the Web. The Library history manager provides a basic
110: set of functionality to keep track of a linear history list.
2.1 frystyk 111: <PRE>
2.2 frystyk 112: #include "<A HREF="HTHist.html">HTHist.h</A>"
2.1 frystyk 113: </PRE>
2.12 eric 114: <P>
2.1 frystyk 115: End of application specific modules
116: <PRE>
117: #ifdef __cplusplus
118: } /* end extern C definitions */
119: #endif
120:
121: #endif
122: </PRE>
2.12 eric 123: <P>
124: <HR>
2.10 frystyk 125: <ADDRESS>
2.13 ! frystyk 126: @(#) $Id: WWWApp.html,v 2.12 1996/05/15 22:34:43 eric Exp $
2.10 frystyk 127: </ADDRESS>
2.12 eric 128: </BODY></HTML>
Webmaster
![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to WWWApp.html CVS log ![[TXT]](/cvsweb/icons/text.gif){kind=icon}
![[DIR]](/cvsweb/icons/dir.gif){kind=icon}
Up to [Public] / libwww / Library / src