[BACK]Return to HTBind.html CVS log [TXT] [DIR] Up to [Public] / libwww / Library / src

Diff for /libwww/Library/src/HTBind.html between versions 2.17 and 2.18

version 2.17, 1998/05/14 02:10:17 version 2.18, 1999/06/30 21:05:13
Line 14 Line 14
 */  */
 </PRE>  </PRE>
 <P>  <P>
 This module sets up the binding between a file suffix and a media type, language,  The preferences that we described in section
 encoding etc. In a client application the suffixes are used in protocols  <A HREF="../User/Using/Prefs.html">Request Preferences</A> did not mention
 that does not directly support media types etc., like FTP, and in server  what libwww should do if it doesn't know the data format of a document. In
 applications they are used to make the bindings between the server and the  many protocols this information is provided by the remote server. Typical
 local file store that the server can serve to the rest of the world (well  examples are MIME like protocols where the metainformation such as the
 almost). The <A HREF="HTFormat.html">HTFormat module</A> holds this information  <EM>Content-Type</EM> and the <EM>Content-Language</EM> is provided together
 against the accept headers received in a request and uses if for format  with the document. However, applications often have access to the local file
 negotiation. All the binding management can all be replace by a database  system using <B>file</B> URLs which in general do not keep any or at least
 interface.  very little information of the file type. It is therefore required to have
   some kind of binding between the file system and the preferences registered
   in the Library which provides this mateinformation about the object.
   <P>
   Often files in a file system is classified by some sort of a suffix, for
   example, <TT>GIF</TT> files are often ending in <EM>.gif</EM>, text files
   in <EM>.txt</EM> etc. This binding is not static and it is therefore required
   to have a dynamic binding just like the preferences themselves. An example
   of the latter is HTML files which on most Unix systems end in <EM>.html</EM>
   whereas they on many MS-DOS based systems end in <EM>.htm</EM>.
   <P>
   This module provides a generic binding mechanism between a file and its
   representation internally in libwww. It is not limited to simple file suffix
   classification but can also be used in more advanced environments using data
   bases etc. However, at this point we are interested in how we can register
   bindings between file suffixes and for example content types, content languages
   etc. The Bind manager is born with a certain knowledge about the set of
   delimiters but more can be added to provide the functionality desired.
   <P>
   All the binding management could of course be replaced by a database interface.
 <P>  <P>
 This module is implemented by <A HREF="HTBind.c">HTBind.c</A>, and it is  This module is implemented by <A HREF="HTBind.c">HTBind.c</A>, and it is
 a part of the <A HREF="http://www.w3.org/Library/"> W3C Sample Code  a part of the <A HREF="http://www.w3.org/Library/"> W3C Sample Code
Removed from v.2.17  
changed lines
  Added in v.2.18

Webmaster