I'm happy to do it in PHP, and should be able to implement the various
features here. I'd use simple URL-hash based filesystem caching (unless
memcache is an option? -- the scale of the edit counter might justify this).
A RESTful API would be the simplest option, with data output in XML and
possibly JSON/serialized PHP. We could have a couple of settings, e.g.
"Quick Count" (no namespaces or other statistics", "Summary"
(namespaces)
and "Detailed" (count, namespaces, timeline, use of edit summaries etc.).
Presuming it's going to be widely used, we might as well plan it here --
anybody else have structural suggestions for the tool?
On Nov 22, 2007 6:16 AM, E <e.wikipedia(a)gmail.com> wrote:
As suggested before, we should begin to explore the
need of a dedicated
editcounter that is run on the new stable server. The simple fact is that it
would make life easier for many wikis, by providing a fast and reliable
editcounter for users to utilise for any purpose (RfA, RfB, etc.).
Is there anyone that has a editcount utility that would be fine with
hosting it on the stable server?
Thanks in advance,
Kind regards,
E
English Wikipedia
e.wikipedia(a)gmail.com
_______________________________________________
Toolserver-l mailing list
Toolserver-l(a)lists.wikimedia.org
http://lists.wikimedia.org/mailman/listinfo/toolserver-l