Can I ask about the limits on server demand that there are for rating systems? I am thinking about making an implementable version of Ghost-rating, and would like to know how much of a database or how much processing power it would be viable to require.

As long as all functionality is O(1) it should be okay, though server load isn't necessarily the only reason such a patch wouldnt be accepted, you know better than anyone how contentious ranking systems are

A proposal that it would be more interesting IMO would be to make an XML incremental service accessible on phpDip, so that TGM could pull the data when needed and having the ranking on a different server. (Eventually phpDip could poll the ranking back from the external server via another webservice, should kestas ever get convinced by another ranking system).

This would have a broad set of advantages, from greatly reducing security risks to have basically no additional workload for phpDip server. This would also make possible for other devs with other proposals of algorithm to have concurrent alternatives to the ghost-ranking system, so that comparison and cross-pollination would be possible.

The only BIG downside looking at the "todo" list of the .83 is that creating an XML service from the scratch is probably more work than the entire of that list... :-/

Also that adding Ghostrating or the like internally would only require a little more work an another few database values.If you added an xml feed, what would it limit to? I guess you could have a variable to say the gameID you last processed, but even then there's real potential for it to be abused.

Who is online

Users browsing this forum: No registered users and 1 guest

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot post attachments in this forum