<?xml version="1.0"?>
<?xml-stylesheet type="text/css" href="http://test.amule.szerverem.hu/w/skins/common/feed.css?303"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>http://test.amule.szerverem.hu/w/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=80.58.40.172</id>
		<title>AMule Project FAQ - User contributions [en]</title>
		<link rel="self" type="application/atom+xml" href="http://test.amule.szerverem.hu/w/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=80.58.40.172"/>
		<link rel="alternate" type="text/html" href="http://test.amule.szerverem.hu/wiki/Special:Contributions/80.58.40.172"/>
		<updated>2026-04-05T19:35:45Z</updated>
		<subtitle>User contributions</subtitle>
		<generator>MediaWiki 1.23.3</generator>

	<entry>
		<id>http://test.amule.szerverem.hu/wiki/AMuleWeb</id>
		<title>AMuleWeb</title>
		<link rel="alternate" type="text/html" href="http://test.amule.szerverem.hu/wiki/AMuleWeb"/>
				<updated>2004-07-21T19:01:44Z</updated>
		
		<summary type="html">&lt;p&gt;80.58.40.172: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;AMuleWeb is an utility that listens for HTTP connections at port 4711 (by default) and allows remote users to control aMule using just a web browser. &lt;br /&gt;
&lt;br /&gt;
aMule itself doesn't support listening to HTTP connections, so the external utility AMuleWeb is used. This utility listens for remote connections, and once the link between amuleweb and the remote user is established, it connects to the aMule main program using the [[External_Connections]] mechanism.&lt;/div&gt;</summary>
		<author><name>80.58.40.172</name></author>	</entry>

	<entry>
		<id>http://test.amule.szerverem.hu/wiki/AMuleWeb</id>
		<title>AMuleWeb</title>
		<link rel="alternate" type="text/html" href="http://test.amule.szerverem.hu/wiki/AMuleWeb"/>
				<updated>2004-07-21T18:55:57Z</updated>
		
		<summary type="html">&lt;p&gt;80.58.40.172: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;aMule utility that listens for HTTP connections at port 4711 (by default). Once the link between amuleweb and the remote user is established, it connects to the aMule main program using the [[External_Connections]] mechanism.&lt;/div&gt;</summary>
		<author><name>80.58.40.172</name></author>	</entry>

	<entry>
		<id>http://test.amule.szerverem.hu/wiki/External_Connections</id>
		<title>External Connections</title>
		<link rel="alternate" type="text/html" href="http://test.amule.szerverem.hu/wiki/External_Connections"/>
				<updated>2004-07-21T18:51:46Z</updated>
		
		<summary type="html">&lt;p&gt;80.58.40.172: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;''Note: Since there's no info at all about this, I'll write what I think External Connections are. I'm no expert so I may be wrong, so take the following with a grain of salt. If some experts thinks this info is right, then please remove this comment (and if it's not, please correct it and remove the comment anyway! ;-) ).''&lt;br /&gt;
&lt;br /&gt;
External connections are the way aMule has to communicate with external utilities, like the webserver. So, when an user is controlling aMule remotely with a web browser, he's not talking directly with aMule, but with another program (amuleweb in this case) that is who really listens at port 4711. This program then talks with aMule using the external connections mechanism.&lt;br /&gt;
&lt;br /&gt;
Since usually both aMule and their utilities run on the same machine, there's no need to redirect the external connections port in a firewalled environment (NAT network with a router, etc.).&lt;/div&gt;</summary>
		<author><name>80.58.40.172</name></author>	</entry>

	</feed>