[SiRoB]

Pifki, on Mar 20 2006, 11:42 PM, said:

After some testing, i've noticed that when retrying a failed wc block download, it will often gets succesful. This is seems to be really useful for T-Online Proxies.

Why not add a retry for failed downloads? 5 retries would be ok.

Retry on what? Failed connection or failed transfer?
If you speak about connection there is always 3 attempt...
If you speak about failed transfer there is already 5 retransmits before killing the transfer...

[Pifki]

SiRoB, on Mar 21 2006, 07:41 AM, said:

Pifki, on Mar 20 2006, 11:42 PM, said:

After some testing, i've noticed that when retrying a failed wc block download, it will often gets succesful. This is seems to be really useful for T-Online Proxies.

Why not add a retry for failed downloads? 5 retries would be ok.

Retry on what? Failed connection or failed transfer?
If you speak about connection there is always 3 attempt...
If you speak about failed transfer there is already 5 retransmits before killing the transfer...

That's right, but only for normal transfers. WebCache doesn't retry after an error, when downloading a cached block.

[SiRoB]

Well webcache traffic are TCP connection,
so 3 SYN for the connection part then 5 retry for data transfer. (for a a standard configuration)
If the http server can't handle your connection or abort the connection, this mean it is maybe overloaded.
So keep hamering it should be worst.

[SiRoB]

Hi every one,

if you are looking for a webcache client based to 0.47a, you may have give a try to the latest MorphXT version (8.9).
It's the first mod based on WebCache v2 core, that finaly work.

Good testing, if you want to make report about your test or experience you may have to post here.

Happy WE.

[tHeWiZaRdOfDoS]

Saw it and might also check out the changes... however, a pure 0.47a WC client would be nice2have


EDIT:
you still access the port via thePrefs.port - won't work with randomports (and isn't good style either)
I also changed some parts in WebCacheProxyClient.cpp, e.g.:

Quote

  POSITION pos = SINGLEProxyClient->reqfile->srclist.Find(this);
  if( pos )
  SINGLEProxyClient->reqfile->RemoveSrcAtPos(pos);

- appears multiple times.

Still reading but it looks pretty interesting...

This post has been edited by tHeWiZaRdOfDoS: 25 March 2006 - 10:56 AM

[SiRoB]

Well Random port is realy nasty for the WebCache feature, as in most of the case you will get a lowid, if you don't know what you are doing.

And for the other report both write are equal.
SINGLEProxyClient->reqfile == reqfile