Quote:
Originally posted by XXXManager
The problem is, that if you all use a software that autonomously and individually access GFY all the time and follows every single page continuously and relentlessly, GFY will crash from overuse ;)
or atleast slow down for no good (for Lensmen) reason...
How is that?
Lets say 5000 users use a software that spiders GFY every lets say 10 minutes to check for stuff, that is extra 5000*6*24=600K index requests. If on every scan there are 10 new threads showing (on a very slow day), its extra 10 times that which is an extra 6M/day That is even before you went to GFY and actually read the threads that interest you, replied, read again, refreshed .
6.6M extra requests a day only for tracking gfy to save you time (which is exactly what Lensmen doesn't want you to do, since the banners here are waiting for you to stare at)... How long do you think will it be before you're gonna be blocked?
I can tell you exactly  less than a day after you get to know that gadget.
Maybe I'm wrong though 
|
There is a very easy workaround for this. You should have a script that will write the contents to a file/db on a server then all
the Ticker clients read the content from that file. That way you
only have 1 client checking the index page and it would cause no
load on GFY.
This approach is a lot better than having all Tickers update from GFY itself. Just have it update from the file that is generated by
1 script that is actually retrieving the index of GFY.
DynaMite