Jeremy Dunck wrote: I've been running some of the scripts yesterday, and they were *way* more responsive. It seems the text access is slowing them down today. After all, not only the page text, but also the templates (and sub-templates and so on) have to be loaded. Sadly, it does not seem to be possible to load text directly from the toolserver database for current or recent versions. Magnus

Hi This is incorrect. The cur-table is not being updated since the days of MediaWiki 1.4. Currently, the only way to get full text reliably is via HTTP, preferably from WikiProxy. Full text is (conceptionally) stored in the `text` table (referenced from the revision table), but in practice that table often just contains pointers to an external storage server, to which we don't have access. I have been told about a few problems with WikiProxy and am currently trying to fix them. I will put a new version live soon. NOTE: this also means that access tokens will soon become necessary if you want to use WikiProxy remotely. Local access from Zedler will work as before. -- Daniel -- Homepage: http://brightbyte.de

Jeremy Dunck schrieb: No. Maybe I should write a Meta page... (I have no experience whatsoever in writing DTDs or the like) 17 minutes to load the text, six seconds to parse it. Strange, I just ran [[en:Texas]] locally, and loadtime was 30 seconds (rendering 4.2 sec). Is there some kind of limiter running on the toolserver? Indeed. Magnus

River Tarnell schrieb: Actually, at this very moment, it seems quite fast (e.g., "missing images"). I can switch my scripts to use either wikiproxy or the direct "&action=raw" request. The latter seems a little slower that wikiproxy during good time, though. Recommendations? Magnus