If the api was only a thin wrapper around some base classes, then indeed you
would not need fauxrequest. However the api does much processing itself and
in practice using fauxrequest is much easier.
Bryan
Op 6 feb 2011 02:29 schreef "Krinkle" :
Ilmari Karonen wrote:
> On 02/06/2011 12:42 AM, Kr
Ilmari Karonen wrote:
> On 02/06/2011 12:42 AM, Krinkle wrote:
>
>> So I was thinking :
>> * upload a mediawiki install (the same version that WMF runs, ie.
>> 1.16wmf4 or 1.17wmf1)
>> * make it not publically accessable (we don't want people actually
>> browsing the wiki)
>> * Configure it in a s
On 02/06/2011 12:42 AM, Krinkle wrote:
> So I was thinking :
> * upload a mediawiki install (the same version that WMF runs, ie.
> 1.16wmf4 or 1.17wmf1)
> * make it not publically accessable (we don't want people actually
> browsing the wiki)
> * Configure it in a special way so that one can use t
Op 5 feb 2011, om 23:49 heeft MZMcBride het volgende geschreven:
> Krinkle wrote:
>> * Configure it in a special way so that one can use the same code for
>> any wiki (ie. a $lang and $family variable of some kind)
>
> The general idea seems fine. My only comment about this proposal is
> that th
Krinkle wrote:
> * Configure it in a special way so that one can use the same code for
> any wiki (ie. a $lang and $family variable of some kind)
The general idea seems fine. My only comment about this proposal is that the
lang/family combination is horrific and should never, ever be used. It ends
Hi all,
I'm finding myself making calls to the live api on the wmf wikis and
thinking: Writing the query from scratch for every detail (or copying
it from the bits and pieces in mw source code) for every time I need
the data is nonsense since it was already done. in mediawiki core.
Medi
