Annotation of libwww/Library/src/WWWApp.html, revision 2.16
2.1 frystyk 1: <HTML>
2: <HEAD>
2.16 ! frystyk 3: <TITLE>W3C Reference Library libwww Client Profile Interface</TITLE>
! 4: <!-- Changed by: Henrik Frystyk Nielsen, 5-Jul-1996 -->
2.1 frystyk 5: </HEAD>
6: <BODY>
2.12 eric 7: <H1>
2.16 ! frystyk 8: Client Profile Interface
2.12 eric 9: </H1>
2.1 frystyk 10: <PRE>
11: /*
12: ** (c) COPYRIGHT MIT 1995.
13: ** Please first read the full copyright statement in the file COPYRIGH.
14: */
15: </PRE>
2.12 eric 16: <P>
17: In addition top the basic W3C Reference Library include file called
18: <A HREF="WWWLib.html">WWWLib.h</A> you <EM>can</EM> also include this file
19: called WWWApp.h depending on the needs of your application. However, it is
20: not required and none of the files included below are ever used in the core
21: part of the Library itself. Only if this file is included, the extra modules
22: will get included in the linked object code. It is also possible to include
23: only a subset of the files below if the functionality you are after is covered
24: by them.
2.1 frystyk 25: <PRE>
26: #ifndef WWWAPP_H
27: #define WWWAPP_H
28: </PRE>
29: <PRE>
30: #ifdef __cplusplus
31: extern "C" {
32: #endif
33: </PRE>
2.16 ! frystyk 34: <H3>
2.12 eric 35: System dependencies
2.16 ! frystyk 36: </H3>
2.12 eric 37: <P>
2.11 frystyk 38: The <A HREF="sysdep.html">sysdep.h</A> file includes system-specific include
2.12 eric 39: files and flags for I/O to network and disk. The only reason for this file
40: is that the Internet world is more complicated than Posix and ANSI.
2.14 frystyk 41: <PRE>#include "<A HREF="sysdep.html">sysdep.h</A>"
2.11 frystyk 42: </PRE>
2.12 eric 43: <H2>
2.13 frystyk 44: Event Manager
45: </H2>
46: <P>
47: The core part of libwww only provides the hooks for the event manager. There
48: is no event loop internal to the core part. Instead the application must
49: provide the event loop in order to use either pseudo threads or real threads.
50: If the application only uses blocking sockets without threads then it is
51: not required to register any event loop at all. We provide a default
52: implementation of an event loop which you can either take or get some ideas
53: from.
54: <PRE>#include "<A HREF="HTEvntrg.html">HTEvntrg.h</A>"
55: </PRE>
56: <H2>
2.16 ! frystyk 57: Managing the Home Page
2.12 eric 58: </H2>
59: <P>
60: This module provides some "make life easier" functions in order to get the
61: application going. They help you generate the first anchor, also called the
62: <EM>home anchor</EM>. It also contains a nice set of default WWW addresses.
2.2 frystyk 63: <PRE>
64: #include "<A HREF="HTHome.html">HTHome.h</A>"
2.1 frystyk 65: </PRE>
2.12 eric 66: <H2>
67: User Dialogs and Messages
68: </H2>
69: <P>
70: You can register a set of callback functions to handle user prompting, error
71: messages, confimations etc. Here we give a set of functions that can be used
72: on almost anu thinkable platform. If you want to provide your own platform
73: dependent implementation then fine :-)
2.8 frystyk 74: <PRE>
75: #include "<A HREF="HTDialog.html">HTDialog.h</A>"
76: </PRE>
2.12 eric 77: <H2>
2.14 frystyk 78: Load, Upload, and Search URLs
79: </H2>
80: <P>
81: Even though you may use the API for the HTRequest object directly in order
82: to issue a request, you will probably find that in real life it is easier
83: to use a higher level abstraction API. This API is provided by the
84: <A HREF="HTAccess.html">HTAccess module</A> where you will find all kind
85: of functions for down loading a URL etc.
86: <PRE>
87: #include "<A HREF="HTAccess.html">HTAccess.h</A>"
88: </PRE>
89: <H2>
2.16 ! frystyk 90: BEFORE and AFTER Filters
2.12 eric 91: </H2>
92: <P>
2.16 ! frystyk 93: <I>Before</I> a request has been issued and <I>after</I> it has terminated
! 94: the application often has to do some action as a result of the request (and
! 95: of the result of the request). The Client Profile Interface Library provides
! 96: a set of standard BEFORE and AFTER filters to handle <I>caching</I>,
! 97: <I>redirection</I>, <I>authentication</I>, <I>logging</I> etc.
! 98: <PRE>
! 99: #include "<A HREF="HTFilter.html">HTFilter.h</A>"
! 100: </PRE>
2.12 eric 101: <H3>
102: Logging
103: </H3>
104: <P>
105: Often it is required to log the requests issued to the Library. This can
106: either be the case if the application is a server or it can also be useful
107: in a client application. This module provides a simple logging mechanism
108: which can be enabled if needed.
2.1 frystyk 109: <PRE>
2.2 frystyk 110: #include "<A HREF="HTLog.html">HTLog.h</A>"
2.1 frystyk 111: </PRE>
2.16 ! frystyk 112: <H2>
2.12 eric 113: History Management
2.16 ! frystyk 114: </H2>
2.12 eric 115: <P>
116: Another type of logging is keeping track of which documents a user has visited
117: when browsing along on the Web. The Library history manager provides a basic
118: set of functionality to keep track of a linear history list.
2.1 frystyk 119: <PRE>
2.2 frystyk 120: #include "<A HREF="HTHist.html">HTHist.h</A>"
2.1 frystyk 121: </PRE>
2.12 eric 122: <P>
2.1 frystyk 123: End of application specific modules
124: <PRE>
125: #ifdef __cplusplus
126: } /* end extern C definitions */
127: #endif
128:
129: #endif
130: </PRE>
2.12 eric 131: <P>
132: <HR>
2.10 frystyk 133: <ADDRESS>
2.16 ! frystyk 134: @(#) $Id: WWWApp.html,v 2.15 1996/07/04 18:44:44 frystyk Exp $
2.10 frystyk 135: </ADDRESS>
2.12 eric 136: </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