35 lines
1.4 KiB
HTML
35 lines
1.4 KiB
HTML
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
|
|
"http://www.w3.org/TR/html4/loose.dtd">
|
|
<html lang="en"><head><title>SAM proxy - Wikipedia</title>
|
|
<meta http-equiv="Content-type" content="text/html; charset=utf-8">
|
|
<meta name="robots" content="index,follow">
|
|
<link rel="shortcut icon" href="/favicon.ico">
|
|
<style type='text/css'><!--
|
|
/*/*/
|
|
a.new, #quickbar a.new { color: #CC2200; }
|
|
#quickbar { position: absolute; top: 4px; left: 4px; border-right: 1px solid gray; }
|
|
#article { margin-left: 152px; margin-right: 4px; }
|
|
/* */
|
|
//--></style>
|
|
</head>
|
|
|
|
<body bgcolor='#FFFFFF' onload=''>
|
|
<h1 class='pagetitle'>SAM proxy</h1><p class='subtitle'>From Python-I2P.
|
|
|
|
|
|
<div class='bodytext'>
|
|
A <strong>SAM proxy</strong> is run by the I2P router. The proxy allows streams, datagrams, and raw packets to be sent through the I2P network. A client application uses a telnet-like session to communicate with the proxy. In this way, the core features of the I2P library can be used by any language.
|
|
|
|
|
|
<p>
|
|
The protocol used for SAM is described in <a href='http://dev.i2p.net/pipermail/i2p/2004-July/000353.html' class='printable' title="http://dev.i2p.net/pipermail/i2p/2004-July/000353.html">SAM 1.0</a>.
|
|
|
|
<p>
|
|
In practice, a <em>SAM library</em> is usually written, so that client applications do not need to use the low-level SAM commands.
|
|
|
|
<p>
|
|
</div>
|
|
<p><em>
|
|
|
|
</em><!-- Time since request: 0.77 secs. -->
|
|
</body></html> |