L2HAC - Revision history

Omeringen: Undo revision 2951 by Izegiwera (Talk)

2010-11-18T12:53:05Z

Undo revision 2951 by Izegiwera (Talk)

Izegiwera at 04:38, 18 November 2010

2010-11-18T04:38:38Z

WiZaRd: corrections... not sure about the 58mins?

2007-07-23T08:38:41Z

corrections... not sure about the 58mins?

DavidXanatos: New page: THIS IS NOT FINAL... fill free to edit and add suggestions = Introduction = The Low 2 High Auto Callback is an old protocol extension used by some eMule mods. Because of the new Mod Prot ...

2007-07-23T08:16:36Z

New page: THIS IS NOT FINAL... fill free to edit and add suggestions = Introduction = The Low 2 High Auto Callback is an old protocol extension used by some eMule mods. Because of the new Mod Prot ...

New page

THIS IS NOT FINAL...
fill free to edit and add suggestions

= Introduction =
The Low 2 High Auto Callback is an old protocol extension used by some eMule mods. Because of the new Mod Prot it is needed to be updated.
The main idea is simple when a LowID source have a HighID client in his queue he will establish a connection for reask to the HighID on its own and the HighID will use it instead of triggering server/kad/xs based callbacks.

= Specification =
A mod announces the support for this feature in the common mod info tag (1 bit), if booth clients have set the bit than the HighID will not trigger any callbacks unless 59 minutes passed by since the last connection he had to the LowID, the LowID should automatically callback in 29 (normal) or 48 (nnp) minutes intervals, the exact callback interval can be chosen freely by the LowID from between 29 and 48 minutes.

[[category:Mod_protocol_extensions]]

@@ Line 2: / Line 2: @@
 feel free to edit and add suggestions
->= Introduction =
+= Introduction =
 The Low 2 High Auto Callback is an old protocol extension used by some eMule mods and the eMulePlus client. Because of the new Mod Prot it requires an update.
 The main idea is simple: when a LowID source has a HighID client in his queue he will establish a connection to reask the HighID on its own and the HighID will use it instead of triggering server/kad/xs based callbacks.
 That way, callback overhead is reduced.
 = Specification =

@@ Line 2: / Line 2: @@
 feel free to edit and add suggestions
-= Introduction =
+>= Introduction =
 The Low 2 High Auto Callback is an old protocol extension used by some eMule mods and the eMulePlus client. Because of the new Mod Prot it requires an update.
 The main idea is simple: when a LowID source has a HighID client in his queue he will establish a connection to reask the HighID on its own and the HighID will use it instead of triggering server/kad/xs based callbacks.
 That way, callback overhead is reduced.
 = Specification =

@@ Line 1: / Line 1: @@
 THIS IS NOT FINAL...
-fill free to edit and add suggestions
+feel free to edit and add suggestions
 = Introduction =
-The Low 2 High Auto Callback is an old protocol extension used by some eMule mods. Because of the new Mod Prot it is needed to be updated.
+The Low 2 High Auto Callback is an old protocol extension used by some eMule mods and the eMulePlus client. Because of the new Mod Prot it requires an update.
-The main idea is simple when a LowID source have a HighID client in his queue he will establish a connection for reask to the HighID on its own and the HighID will use it instead of triggering server/kad/xs based callbacks.
+The main idea is simple: when a LowID source has a HighID client in his queue he will establish a connection to reask the HighID on its own and the HighID will use it instead of triggering server/kad/xs based callbacks.
 = Specification =
-A mod announces the support for this feature in the common mod info tag (1 bit), if booth clients have set the bit than the HighID will not trigger any callbacks unless 59 minutes passed by since the last connection he had to the LowID, the LowID should automatically callback in 29 (normal) or 48 (nnp) minutes intervals, the exact callback interval can be chosen freely by the LowID from between 29 and 48 minutes.
+A mod announces the support for this feature in the common mod info tag (1 bit), if both clients have set the bit than the HighID will not trigger any callbacks unless 59 minutes passed by since the last connection he had to the LowID, the LowID should automatically callback in 29 (normal) or 58 (nnp) minute intervals, the exact callback interval can be chosen freely by the LowID from 29 to 58 minutes.
 [[category:Mod_protocol_extensions]]