1
0
Fork 0
cl-sites/guile.html_node/Web.html
2024-12-17 12:49:28 +01:00

113 lines
5.3 KiB
HTML

<!DOCTYPE html>
<html>
<!-- Created by GNU Texinfo 7.1, https://www.gnu.org/software/texinfo/ -->
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<!-- This manual documents Guile version 3.0.10.
Copyright (C) 1996-1997, 2000-2005, 2009-2023 Free Software Foundation,
Inc.
Copyright (C) 2021 Maxime Devos
Copyright (C) 2024 Tomas Volf
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.3 or
any later version published by the Free Software Foundation; with no
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled "GNU Free
Documentation License." -->
<title>Web (Guile Reference Manual)</title>
<meta name="description" content="Web (Guile Reference Manual)">
<meta name="keywords" content="Web (Guile Reference Manual)">
<meta name="resource-type" content="document">
<meta name="distribution" content="global">
<meta name="Generator" content=".texi2any-real">
<meta name="viewport" content="width=device-width,initial-scale=1">
<link href="index.html" rel="start" title="Top">
<link href="Concept-Index.html" rel="index" title="Concept Index">
<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
<link href="Guile-Modules.html" rel="up" title="Guile Modules">
<link href="getopt_002dlong.html" rel="next" title="getopt-long">
<link href="POSIX.html" rel="prev" title="POSIX">
<style type="text/css">
<!--
a.copiable-link {visibility: hidden; text-decoration: none; line-height: 0em}
span:hover a.copiable-link {visibility: visible}
-->
</style>
<link rel="stylesheet" type="text/css" href="https://www.gnu.org/software/gnulib/manual.css">
</head>
<body lang="en">
<div class="section-level-extent" id="Web">
<div class="nav-panel">
<p>
Next: <a href="getopt_002dlong.html" accesskey="n" rel="next">The (ice-9 getopt-long) Module</a>, Previous: <a href="POSIX.html" accesskey="p" rel="prev"><abbr class="acronym">POSIX</abbr> System Calls and Networking</a>, Up: <a href="Guile-Modules.html" accesskey="u" rel="up">Guile Modules</a> &nbsp; [<a href="index.html#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="Concept-Index.html" title="Index" rel="index">Index</a>]</p>
</div>
<hr>
<h3 class="section" id="HTTP_002c-the-Web_002c-and-All-That"><span>7.3 <abbr class="acronym">HTTP</abbr>, the Web, and All That<a class="copiable-link" href="#HTTP_002c-the-Web_002c-and-All-That"> &para;</a></span></h3>
<a class="index-entry-id" id="index-Web"></a>
<a class="index-entry-id" id="index-WWW"></a>
<a class="index-entry-id" id="index-HTTP"></a>
<p>It has always been possible to connect computers together and share
information between them, but the rise of the World Wide Web over the
last couple of decades has made it much easier to do so. The result is
a richly connected network of computation, in which Guile forms a part.
</p>
<p>By &ldquo;the web&rdquo;, we mean the HTTP protocol<a class="footnote" id="DOCF25" href="#FOOT25"><sup>25</sup></a> as handled by
servers, clients, proxies, caches, and the various kinds of messages and
message components that can be sent and received by that protocol,
notably HTML.
</p>
<p>On one level, the web is text in motion: the protocols themselves are
textual (though the payload may be binary), and it&rsquo;s possible to create
a socket and speak text to the web. But such an approach is obviously
primitive. This section details the higher-level data types and
operations provided by Guile: URIs, HTTP request and response records,
and a conventional web server implementation.
</p>
<p>The material in this section is arranged in ascending order, in which
later concepts build on previous ones. If you prefer to start with the
highest-level perspective, see <a class="pxref" href="Web-Examples.html">Web Examples</a>, and work your way
back.
</p>
<ul class="mini-toc">
<li><a href="Types-and-the-Web.html" accesskey="1">Types and the Web</a></li>
<li><a href="URIs.html" accesskey="2">Universal Resource Identifiers</a></li>
<li><a href="HTTP.html" accesskey="3">The Hyper-Text Transfer Protocol</a></li>
<li><a href="HTTP-Headers.html" accesskey="4">HTTP Headers</a></li>
<li><a href="Transfer-Codings.html" accesskey="5">Transfer Codings</a></li>
<li><a href="Requests.html" accesskey="6">HTTP Requests</a></li>
<li><a href="Responses.html" accesskey="7">HTTP Responses</a></li>
<li><a href="Web-Client.html" accesskey="8">Web Client</a></li>
<li><a href="Web-Server.html" accesskey="9">Web Server</a></li>
<li><a href="Web-Examples.html">Web Examples</a></li>
</ul>
</div>
<div class="footnotes-segment">
<hr>
<h4 class="footnotes-heading">Footnotes</h4>
<h5 class="footnote-body-heading"><a id="FOOT25" href="#DOCF25">(25)</a></h5>
<p>Yes, the P is for
protocol, but this phrase appears repeatedly in RFC 2616.</p>
</div>
<hr>
<div class="nav-panel">
<p>
Next: <a href="getopt_002dlong.html">The (ice-9 getopt-long) Module</a>, Previous: <a href="POSIX.html"><abbr class="acronym">POSIX</abbr> System Calls and Networking</a>, Up: <a href="Guile-Modules.html">Guile Modules</a> &nbsp; [<a href="index.html#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="Concept-Index.html" title="Index" rel="index">Index</a>]</p>
</div>
</body>
</html>