Ævar Arnfjörð Bjarmason wrote:
P.s.: not that I wouldn't mind something like a general robot interface, in fact, I voulenteer to (help) write one (if thats something the people with CVS access would be willing to accept that is).
This would be a huge help to me, since I have very little experience with PHP. I'm thinking some kind of webservices-like API that follows REST principles (ie not SOAP!)
I can already do most things on the client, but a few things are needed to allow alternative interfaces to fly:
- action=getedittoken - returns just an edit token
- Special:Random&action=raw gives the raw content of a random page
- Special:Export?title=RecentChanges gives an XML list of recent changes
None of these things need any major architectural changes.
Jim
Rather than having some quick hack made just for you it would probably be better to consider well how to make a standard interface for something like this, something like action=robot which would return something in an easy-to-parse format, is there a bug open for this already where something like this could be brainstormed?
Yes, I agree. However, it should not be assumed that the agent is a robot, it may be a thick client written (like mine) in AJAX, GTK or some other thing.
I'm not sure what you mean by an easy to parse format? Just sending the token as 32 plaintext chars seems as easy as it could possibly be.
In the meantime, as I understand it what you need *now* is to just implement this on your own wiki, would it not be an option to just modify the code you use to not require the token?
Well, yes, but for my project, not for my wiki. My intention is to provide a mediawiki interface that can be used on any interface. My wiki is really only for the purpose of testing and demonstrating that interface.
What I am really trying to do is bring down the number of Apache machines needed to serve a big wiki to maybe a quarter what it is now. Serving static content is really, really cheap.
-- Jim