As per a request by sporty we will start adding a new attribute to the XML tickers that will show what PerlMonks considers to be the minimum acceptable time between polling that ticker. This infomation will be available through the 'min_poll_seconds' attribute of the INFO element that is supplied with the ticker. (At the time of writing this post only the Private Message XML Ticker provides this attribute, but as soon as we can we will add it to the rest.)

Any client utilizing the XML feeds is expected to comply with this value if it is provided. So essentially the first fetch from a ticker will tell you how often you can fetch from it. If no such value is provided then please use as conservative a delay as possible. Anything more frequent than twice a minute is almost certainly too often. Remember we all have to share the site, so if in doubt err on the side of lower load.

(Update)Note: Its important that clients are written to check this attribute every time they get a response, especially if they are long running. We want to be able to tweak these parameters for all clients from PM, so dont just fetch once and then use that until process termination. You should code your client so that if the value changes so does your polling frequency.

Thanks for you compliance, and patience, but overall the changes being made to the XML tickers should benefit us all through lower DB loads, and extra features.


---
demerphq

    First they ignore you, then they laugh at you, then they fight you, then you win.
    -- Gandhi


Replies are listed 'Best First'.
Re: XML Ticker Refresh Rates
by eric256 (Parson) on Aug 05, 2004 at 15:27 UTC

    I've been a bit curious about these load worries. I don't understand why this site has such problems, although I would say its great right now and I seldom see any slowness like was the norm a year ago but there seems to be a constant worry among the monks. Is it because of the quality of the server or the service? I understand its a free site with little to no means of makeing money so I could see that as being the limiting factor. Is it because of the everything engine? Is it realy that slow that it can't handle XML requests too often? Or is the population here realy so huge as to put the website under? I know full well I might have missed the mark completley here so feel free to straighten me out. If XML requests are that big of issue, wouldn't a caching solution that updated at perlmonks preffered minimum be a good idea? Then clients that tried to refresh more often would just get the same info and there should poll less since polling more gets them no benefit. Just a curiousity not a gripe or anything so plase don't take this all the wrong way.


    ___________
    Eric Hodges