ECv2 - Revision history

Vollstrecker: Language Link

2007-09-02T15:03:56Z

Language Link

82.49.157.253 at 17:05, 4 January 2006

2006-01-04T17:05:50Z

82.49.157.253 at 17:04, 4 January 2006

2006-01-04T17:04:05Z

GonoszTopi at 00:38, 1 March 2005

2005-03-01T00:38:49Z

Jacobo221 at 17:48, 9 December 2004

2004-12-09T17:48:55Z

New page

''ECv2'' stands for ''[[External Connections]] 2.0''.

It is a complete rewrite of the old [[External Connections]] code, mainly designed by [[User:GonoszTopi|GonoszTopi]] with help from [[User:phoenix|phoenix]] and [[User:lfroen|lfroen]].

This new version (starting from [[aMule]] 2.0.0-rc8) is incompatible with any previous version.

The necessity to redisign the [[External Connections]] code came from a security hole a user reported and had to be quickly patched. After fixing it, it became obvious that the protocol's design wasn't felxible, secure and fast enough to have it as a standard protocol for any future application trying to connect to [[aMule]].

The main goal of this protocol is to make it binnary (up to now, it was strings-driven) and to enforce it's security. Apart from that, many care has been taken in make it as fast and flexible as possible. It has become so complex that it can now be considered an [http://en.wikipedia.org/wiki/Application_layer Application layer] (in the [http://en.wikipedia.org/wiki/OSI_model OSI model]).

The new protocol's design specification can be found in the docs that come alogn with the [[aMule]] tarball.

← Older revision		Revision as of 15:03, 2 September 2007
Line 1:		Line 1:
		+	<center>'''English''' \| [[ECv2-de\|Deutsch]]</center>
		+
	''ECv2'' stands for ''[[External Connections]] 2.0''.		''ECv2'' stands for ''[[External Connections]] 2.0''.

@@ Line 7: / Line 7: @@
 The necessity to redisign the [[External Connections]] code came from a security hole a user reported and had to be quickly patched. After fixing it, it became obvious that the protocol's design wasn't flexible, secure and fast enough to have it as a standard protocol for any future application trying to connect to [[aMule]].
-The main goal of this protocol is to make it binnary (up to now, it was strings-driven) and to enforce its security. Apart from that, many care has been taken in make it as fast and flexible as possible. It has become so complex that it can now be considered an [http://en.wikipedia.org/wiki/Application_layer Application layer] (in the [http://en.wikipedia.org/wiki/OSI_model OSI model]).
+The main goal of this protocol is to make it binary (up to now, it was strings-driven) and to enforce its security. Apart from that, much care has been taken in making it as fast and flexible as possible. It has become so complex that it can now be considered an [http://en.wikipedia.org/wiki/Application_layer Application layer] (in the [http://en.wikipedia.org/wiki/OSI_model OSI model]).
 The new protocol's design specification can be found in the docs that come along with the [[aMule]] tarball.

@@ Line 7: / Line 7: @@
 The necessity to redisign the [[External Connections]] code came from a security hole a user reported and had to be quickly patched. After fixing it, it became obvious that the protocol's design wasn't flexible, secure and fast enough to have it as a standard protocol for any future application trying to connect to [[aMule]].
-The main goal of this protocol is to make it binnary (up to now, it was strings-driven) and to enforce it's security. Apart from that, many care has been taken in make it as fast and flexible as possible. It has become so complex that it can now be considered an [http://en.wikipedia.org/wiki/Application_layer Application layer] (in the [http://en.wikipedia.org/wiki/OSI_model OSI model]).
+The main goal of this protocol is to make it binnary (up to now, it was strings-driven) and to enforce its security. Apart from that, many care has been taken in make it as fast and flexible as possible. It has become so complex that it can now be considered an [http://en.wikipedia.org/wiki/Application_layer Application layer] (in the [http://en.wikipedia.org/wiki/OSI_model OSI model]).
 The new protocol's design specification can be found in the docs that come along with the [[aMule]] tarball.

@@ Line 5: / Line 5: @@
 This new version (starting from [[aMule]] 2.0.0-rc8) is incompatible with any previous version.
-The necessity to redisign the [[External Connections]] code came from a security hole a user reported and had to be quickly patched. After fixing it, it became obvious that the protocol's design wasn't felxible, secure and fast enough to have it as a standard protocol for any future application trying to connect to [[aMule]].
+The necessity to redisign the [[External Connections]] code came from a security hole a user reported and had to be quickly patched. After fixing it, it became obvious that the protocol's design wasn't flexible, secure and fast enough to have it as a standard protocol for any future application trying to connect to [[aMule]].
 The main goal of this protocol is to make it binnary (up to now, it was strings-driven) and to enforce it's security. Apart from that, many care has been taken in make it as fast and flexible as possible. It has become so complex that it can now be considered an [http://en.wikipedia.org/wiki/Application_layer Application layer] (in the [http://en.wikipedia.org/wiki/OSI_model OSI model]).
-The new protocol's design specification can be found in the docs that come alogn with the [[aMule]] tarball.
+The new protocol's design specification can be found in the docs that come along with the [[aMule]] tarball.