Annotation of libwww/Library/src/WWWCache.html, revision 2.4
2.1 frystyk 1: <HTML>
2: <HEAD>
2.2 frystyk 3: <TITLE>W3C Reference Library libwww PERSISTENT CACHE</TITLE>
2.4 ! frystyk 4: <!-- Changed by: Henrik Frystyk Nielsen, 16-Apr-1996 -->
2.1 frystyk 5: <NEXTID N="z11">
6: </HEAD>
7: <BODY>
8:
9: <H1>Declaration of W3C Reference PERSISTENT CACHE MODULE</H1>
10:
11: <PRE>
12: /*
13: ** (c) COPYRIGHT MIT 1995.
14: ** Please first read the full copyright statement in the file COPYRIGH.
15: */
16: </PRE>
17:
18: <H3>Cache Manager</H3>
19:
20: Caching is a required part of any efficient Internet access
21: applications as it saves bandwidth and improves access performance
22: significantly in almost all types of accesses. The Library supports
23: two different types of cache: The memory cache and the file cache. The
24: two types differ in several ways which reflects their two main
25: purposes: The memory cache is for short term storage of graphic
26: objects whereas the file cache is for intermediate term storage of
27: data objects. Often it is desirable to have both a memory and a file
28: version of a cached document, so the two types do not exclude each
29: other. <P>
30:
31: The cache contains details of temporary disk files which contain the
32: contents of remote documents. There is also a <A
33: HREF="HTAnchor.html#z1">list of cache items for each URL</A> in its
34: anchor object. <P>
35:
36: There are various ways of handling Expires header when met in a
37: history list. Either it can be ignored all together, the user can be
38: notified with a warning, or the document can be reloaded
39: automatically. This flag decides what action to be taken. The default
40: action is HT_EXPIRES_IGNORE. In HT_EXPIRES_NOTIFY mode you can specify
41: a message to tell the user (NULL is valid in which case my own message
42: pops up - watch out it might be in Danish ;-)) <P>
43:
44: The Library has two notions of a local cache: a file cache and a
45: memory cache. The memory cache is handled by the client and the file
46: cache is handled by the Library. Often the format of a object cached
47: in memory is in the form of a hypertext object ready to be displayed
48: (that is, it's already parsed).
49:
50: <PRE>
51: #ifndef WWWCACHE_H
52: #define WWWCACHE_H
53: </PRE>
54:
55: <PRE>
56: #ifdef __cplusplus
57: extern "C" {
58: #endif
59: </PRE>
60:
2.4 ! frystyk 61: <H2>System dependencies</H2>
! 62:
! 63: The <A HREF="sysdep.html">sysdep.h</A> file includes system-specific include
! 64: files and flags for I/O to network and disk. The only reason for this
! 65: file is that the Internet world is more complicated than Posix and
! 66: ANSI.
! 67:
2.1 frystyk 68: <PRE>
2.4 ! frystyk 69: #include "sysdep.h"
! 70: </PRE>
! 71:
! 72: <H2>Library Includes</H2>
! 73:
! 74: <PRE>
2.1 frystyk 75: #include "HTCache.h"
76: </PRE>
77:
78: End of CACHE module
79:
80: <PRE>
81: #ifdef __cplusplus
82: } /* end extern C definitions */
83: #endif
84:
85: #endif
86: </PRE>
87:
2.3 frystyk 88: <HR>
89: <ADDRESS>
2.4 ! frystyk 90: @(#) $Id: WWWCache.html,v 2.3 1996/04/12 17:50:00 frystyk Exp $
2.3 frystyk 91: </ADDRESS>
2.1 frystyk 92: </BODY>
93: </HTML>
Webmaster