Just an idea, not sure if its good:
Would it make sense to keep synced version of the mediawiki software
itself on the tools server, but only allow localhost api.php access??
This way all the queries, namespace localization and resolution,
redirects, possibly even page parsing and html rendering, and lots of
other logic that will keep changing with the schema as part of the api
will be transparently available, and the tools will be able to use
both local and real wiki api transparently, but local ones at much
higher speed? Additional tool-server specific queries can also be
added to the api since it allows that. On top of it, the API allows
internal PHP access - so any tool server applications that use php can
use the API transparently, without going over http.
If you haven't seen it yet, its at http://en.wikipedia.org/w/api.php
On 7/28/07, Tangotango <tangotango.wp(a)gmail.com> wrote:
WikiProxy is great, Daniel! Thanks for making such a
for accessing text :-)
I have one question: is it possible to access the data WikiProxy
holds without using HTTP? (For example, using PHP's CLI SAPI or
direct inclusion of the WikiProxy library). You mention that you're
concerned about PHP startup times, and I guess the latter method
would alleviate that to some extent.
On Jul 28, 2007, at 9:45 PM, Daniel Kinzler wrote:
To use WikiProxy, you can go to
in the form.
This will only work from the toolserver, though - for access from
you need an access token, available on request.
To use it programmatically, use a URL like the following:
* rev=12345 if you want a specific revision
* ns=5 if title is an un-prefixed page name (you can also use
canonical or local
The wiki parameter accepts names like "de", "dewiki", or
Please try it and tell me if you experience any problems.
Toolserver-l mailing list