Aquileo | Recent changes to feature-requestshttps://sourceforge.net/p/gwcii/feature-requests/2004-07-09T20:12:13ZRecent changes to feature-requestsAquileo | Seperate URL and Host count2004-07-09T20:12:13Z2004-07-09T20:12:13ZPhilipp Winklerhttps://sourceforge.net/u/phwinkler/https://sourceforge.net193b32804dcb6911faf609d0108ce1962b8e3c6d<div class="markdown_content"><p>It would be nice if one could seperate how many host<br />
are given back to the client and how many URL´s are.</p>
<p>I´d like to give back 50 hosts and 10 urls´s for example.</p></div>Aquileo | Function to delete stale hosts2004-05-21T22:15:18Z2004-05-21T22:15:18ZFrosty192https://sourceforge.net/u/frosty192/https://sourceforge.netd3fa56221498939466fe48f91c77306d01a8537b<div class="markdown_content"><p>There is a function to delete url's from the database<br />
after MAX_AGE but there is no function to delete host<br />
ip's. For example gzip.bounceme.net/gwcii.php?stats=1<br />
has 20,000+ hosts stored.</p>
<p>The result of this is that a huge number of stale hosts<br />
are stored and when the script selects this bloated<br />
table it may put a heavy load on the server.</p></div>Aquileo | Seperate settings for host age and url age2004-03-30T22:23:21Z2004-03-30T22:23:21ZFrosty192https://sourceforge.net/u/frosty192/https://sourceforge.net10bc6c7e93fb7de633d7e6e6aad2d55af090682a<div class="markdown_content"><p>There needs to be a seperate setting for IP age and url<br />
age.<br />
If you could store hosts for a short time the pool of<br />
host IP's would be younger and more likely to still be<br />
connected.(4-8 hours, maybe longer depending on cache<br />
usage)<br />
Then you could store url's for a longer time as these<br />
addresses do not change much.(8-10 days)</p></div>Aquileo | Slim down the data files2004-03-30T19:02:27Z2004-03-30T19:02:27ZJoe Julianhttps://sourceforge.net/u/userid-927951/https://sourceforge.net24baea53b664d40ddb1a28c7e52caf5bd69654d8<div class="markdown_content"><p>The stats accumulation seems to be killing off some <br />
caches. There needs to be an option to slim it down <br />
significantly. The slimming should take place by <br />
summarizing stats at some user specified interval into <br />
interval totals, and into a daily total.</p></div>Aquileo | Track bandwidth usage2004-03-13T17:29:54Z2004-03-13T17:29:54ZJoe Julianhttps://sourceforge.net/u/userid-927951/https://sourceforge.net9febf83cdbc42084d8839d685e9628ac83c7b4af<div class="markdown_content"><p>Let's implement some bandwidth tracking using buffering <br />
and ob_get_length</p></div>Aquileo | Move all the HTML code into includes2004-03-13T17:26:03Z2004-03-13T17:26:03ZJoe Julianhttps://sourceforge.net/u/userid-927951/https://sourceforge.netcb95473eaf2b7fcaaa3e81f0efb031f0ac90d1a7<div class="markdown_content"><p>Move all the HTML pages into external includes so they <br />
can be prettied up with css</p></div>Aquileo | support cluster keyword in beta spec2004-03-12T06:26:21Z2004-03-12T06:26:21ZPaul Williamshttps://sourceforge.net/u/aviancer/https://sourceforge.net5f39af6bb30f50ab4e12f3d4d5a8744eedb58769<div class="markdown_content"><p>* The GWC2 beta supports the new<br />
"cluster=[keywords]" parameter. This functionality is<br />
currently for testing of this feature, so consider it<br />
"alpha".<br />
* On update requests, if you include the extra<br />
parameter "cluster=keyword1,keyword2,...", these<br />
keywords will be stored along with the host you submit.<br />
* The following limitations are placed on the<br />
keyword string: it may only contain the characters<br />
[A-Za-z0-9.-_:], and it may not be longer than 256<br />
characters (yes, the entire keyword string). -<br />
Characters that aren't allowed are stripped and any<br />
keywords beyond the 256 characters are dropped.<br />
* On get requests, the keywords are returned in the<br />
field after the age parameter, like so:<br />
o H|127.0.0.2:321|400|keyword1,keyword2,... </p></div>Aquileo | Emailing the cache admin2004-03-02T06:07:04Z2004-03-02T06:07:04ZJoe Julianhttps://sourceforge.net/u/userid-927951/https://sourceforge.net8ee2412ef8e48d9990a4a6c426d444acbb6f4483<div class="markdown_content"><p>When database errors occur, email the cache <br />
administrator (but no more than once per X hours).</p>
<p>Ditto when new updates are out, and for other <br />
detectable problems (like "Verification doesn't work on <br />
your system, turn it off").</p></div>Aquileo | Randomize results a little2004-03-02T05:58:10Z2004-03-02T05:58:10ZJoe Julianhttps://sourceforge.net/u/userid-927951/https://sourceforge.net7f5626d12807317a7a25ed368abb6b43aea74cc0<div class="markdown_content"><p>Try to give a more random set of results to queries.</p>
<p>Currently, only the most recent MAX_HOSTS are <br />
returned to the client. I would like to randomize them a <br />
bit and return a MAX_HOSTS selection from the most <br />
recent MAX_HOSTS*2 records.</p></div>Aquileo | Internationalize2004-02-29T02:41:12Z2004-02-29T02:41:12ZJoe Julianhttps://sourceforge.net/u/userid-927951/https://sourceforge.netbbd800a3126171c76bfcb4bdeaa9fb3e71773fcd<div class="markdown_content"><p>I'd like to internationalize the interface</p></div>