Forwarding to mediawiki-api. Shall we keep the discussion centralized?
---------- Forwarded message ---------- From: Simetrical <[EMAIL PROTECTED]> Date: Feb 3, 2008 4:48 PM Subject: Re: [Toolserver-l] Fwd: ATTENTION: query.php will be removed soon To: [email protected] On Feb 3, 2008 4:47 AM, Kalan <[EMAIL PROTECTED]> wrote: > Of course, we could keep it, but read what the head API developer says: > > > Agree, backwards compatibility is important, but it has to be balanced > > with efforts required to maintain query.php.. Every db schema change > > must be looked at to see if query.php must be updated. Internal api > > changes may also impact its functions and performance. IIRC, there are > > already some queries not working as intended. > <http://lists.wikimedia.org/pipermail/mediawiki-api/2008-February/000347.html> So isn't the obvious answer to rewrite query.php so that it uses api.php as a backend, not just chuck it out the window? Then you only have to care about query.php when you're changing the semantics of api.php's existing parameters, which you shouldn't be doing often anyway. Obviously maintaining query.php as a whole separate backend is stupid, but the backend is separate from the user-exposed interface, which should not change if it can be plausibly avoided. This doesn't sound like a reasonable or correct decision to me. _______________________________________________ Toolserver-l mailing list [email protected] http://lists.wikimedia.org/mailman/listinfo/toolserver-l _______________________________________________ Toolserver-l mailing list [email protected] http://lists.wikimedia.org/mailman/listinfo/toolserver-l
