*************************************************************************************************************************************************************

i2psnarkxl_20101006a.zip
- fixing the HTML spelling bug of RatioControl and Resend options on classicpage
- adding a counter that shows howmany torrents are listed
- including categories - editable by users
- including category filters to the classicpage and theme Postman
- add a new category action "in_use"
 # closely same like the known "active" category but it shows only active torrents those has peers
- include a methode to remove inactive clients automatic from the extented infopage after the given hours; default 72 hours
 # no user setting but changing** by the config file for advanced xl-users is possible. **(before i2p starts)
 # inactive means: not seen by our client since last contact; not listed by any tracker since last contact.
 # config keyname : i2psnarkxl.clients.maxHoursOnListTime=72
 # REM longtime seeders with a lot of autostart torrents should consider to use a value of 2 to reduce the amount of lowlevel threads by the clientinfos
- enhancing theme "Postman" by the new features
 # some browser does not refreshing formular fields by using the refreshbutton of the browser itself, to avoid problems by the category filter when used on different pages during switching the pages i'm adding a "refresh-link" onto the theme postman. 

 # all other included themes are not more supported by me and i'm removing them in one of next releases. 
*********************************************************************************************************
older stuff 

i2psnarkxl_20100928a.zip
md5: 98e68030b964dd40c357fa4a73760893

briefing: (mostly self explaining by the configuration page [classicpage])

- changing the clientID on every new destination too
- store the up/download amount
- including peer setting for (each) torrents
- including max peer setting for all torrents (this prior strikes over the torrent peer setting, when needed)
- including max uploader for (each) torrents
- rewritten some methodes for better performence
- including user setting for ratio control
- including user setting for resend handle by the i2p-router (destination restart required)
- including ratio display for current session and !new! stored amount
- including options that allows you to starting the torrent with your stored values for up/downloads (checked by hash md5)
- including "numwant" and resource handle for tracker request.
- including average displays (up/down)
- including a "Standby Mode" for Leech and Seed (uses the minimum of resources to stay alive with a torrent)
- including autosave (needed to store the up/down amount) [no settings yet, hardcoded 20 minutes]
- changing theme "postman" (to vers 1.6)

-------------------------------------
@ testers:
1.
- I like to know if the new include md5 routine causes problems with non sun-java enviroments! - and if there are any ... how do we resolve it :) -
import java.security.MessageDigest;
import java.security.NoSuchAlgorithmException;
-------------------------------------
2.
- it interesting me how is the long-term behavior of the "Standby Mode" with a couple of Seedfiles (long time seeders).
(my hope is that the rate of long time seeders will growing, since it cost not more that much of resources when holding a torrent as a standby seed)
-------------------
... ???

Please report any problems that hits you here:
http://forum.i2p/viewtopic.php?p=27872#27872 

####################################################################################################################################
http://forum.i2p/viewtopic.php?p=27872#27872 

Posted: Sun Oct 03, 2010 5:25 am     	
	
BlackButterfly wrote:
Ok, some more:
1. postman shows 8 peers and xlsnark only 1, 7 has 0% in postman after some hours
________________

Yeah, thats a good point! I doesn't mention that.
It's a sideeffect of the new included tracker-request-value "numwant" and the dynamic tracker-resource handle around it.
As example. I2PSnark has a static request for numwant of 16.
The result is that you got a max shown number of (16) in I2PSnark. No matter when on the tracker is listed more than 16 peers. There are shown less when the tracker send a less peer amount in return.
the xl tracker-request is dynamic now. when your settings for peers are "10" and you are connected with "8" peers than the next tracker-request will just ask for 2 new peers (+ 4 for reserve) . The result is that the display are only shown (6 or less). no matter how much are listed by the tracker.

I'll see what i can do about this for futured versions.
People expecting the available peercount at this point (and i too).
Current i don't know if the I2P trackers have a value by request for all current listed peers (like we are usually seen by the normal internet bt-clients) or not. i got to figure this out. (on my todo-list now)
########################################
BlackButterfly wrote:

2. where is superseed mode in classic theme?
________________

Since xl exists they were never on the configpage.
It's not a changing by this announced xl-version.
It's from the beginnig at the same place and nobody was disturbed by this right now and current i see no reason to change that.
btw: the themes are still just samples by me and everyone is called to do their own themes and share them with the community!
########################################
BlackButterfly wrote:


3. what is leech value of 0.8? Why cant I change it? (set lower/higher, click save and it is still 0.Cool
________________

It's a mistery for me why you can't change it yet. it should be by default "0.5".
It is the "Ratio Control Level" and by "mouseover" there should popup a short description. "A peer will be choked as long as it get lower then this ratio level."

Do anyone else here have the same problem?! Please announce here!
########################################
BlackButterfly wrote:

4. what is the Overhead resend value?
________________

On "mouseover" there should popup a short description. "how often the I2P-Router should try to resend when failed to connect with a peer."
It belongs to the common tunnel handling by the (i2p) router itselfs and try keeping destinations by proberly usual bad line-connections (??? - correct me if my interpretation is wrong ..)
########################################
BlackButterfly wrote:

and
Peer limit (torrent): peers | ( 10 - 16 ) - I guess max ppers per torrent
Uploader limit (torrent): peers | ( 4 - 6 ) - I do not know this option?
________________

It is the same option like allways was on I2PSnark, just from now it is used as limit for each torrent instead as limit for all torrents like before.
by previously versions it happens often that the allowed uploader peers were all in one torrent and other torrents are untended.
with this new behaviour you force the uploader amount to each torrent.
########################################
BlackButterfly wrote:

standbye ever since the seed has already begun. - what does it mean? nnn minutes after seed started?
________________
Yes! since you started the torrent as a seed or when you was leeching before and finished it during your session -means- since you becoming a seeder ...
"15 - nnn" -> 1 - 999
"nnn" is the max value that matches in the text field.
on the seeder option i used 4 values for the textfield, means you can choose between 15 and 9999 minutes.
########################################
BlackButterfly wrote:

Start torrents with previous Amount - what does it mean?
________________

lets say, you upload 100mb's in a session and restart the torrent than you lost the 100mb's on the display and you start again with 0kb upload.
If you select this option than your next session will starting with the previous stored value of 100mb.
maybe some people like to know what they sharing over all sessions.
the value is used for the tracker announcement too
########################################
BlackButterfly wrote:

And what does standby mode mean at all?
________________

for leeching it means that ... when you are in one of those files where all client 'hanging' with the same percent value and no progress is seen ... than xl "going sleep" and wake up when progress continues.
It remove the unused peers from the list and you have more peer connections for the other torrents.
example: you choose a setting of max peers "30" because you had a tunnelsetting of "3" quantity = (3 in; 3 out) and this bad torrent have 40 leecher that all stocking than there is no free place for new peers by your other torrents.
So why keeping 40 unuset/dead peer-destinations on your tunnels when a small peer amount is enough to keep that torrent alive.
You will stay with 2 (+1) peers and 1 (allowed) uploader.
A 'wheel' logic will allways searching for new peers and changing the current connected peers by a low level task.

closely same function is used by the 'seed" option.
it's realy enough to keep long-term seeds alive.
just try it out with a firstseed of you and you will see that you uploading a 700mb file in closly the same time than usually. just with less resources and upload amount using by yourself.
########################################
