https://bugzilla.wikimedia.org/show_bug.cgi?id=55475

--- Comment #1 from Kunal Mehta (Legoktm) <[email protected]> ---
I started working on some of this.





(In reply to Daniel Friesen from comment #0)


> * Ext: We'll likely need an email handler to send emails through the App
> Engine's mail system.

Created a handler for the AlternateUserMailer hook
(https://github.com/wikimedia/mediawiki-extensions-GoogleAppEngine/blob/master/Hooks.php),
but it could definitely be made more robust.

> * Ext: We'll probably want to kill the normal job queue and find a way to
> implement it using the App Engine's Task Queues api.
> ** It is possible to define a cron job that would run runJobs. But Task
> Queues are much more intelligent. The service works along with the App
> Engine's scaling. If there are no web requests and no tasks the app can
> theoretically be scaled down to the point that there are no instances
> running and costs go down. While cron would regularly warmup a new instance.
> ** We'll want to be wary of extensions that add tasks which have job queue
> items endlessly add themselves back to the job queue to do cron like things.

I did a basic implementation of a JobQueueGAE class which does this:
https://github.com/wikimedia/mediawiki-extensions-GoogleAppEngine/blob/master/job/JobQueueGAE.php

Not sure what can really be done about the extensions that use the job queue as
a cron-like system.

> * Ext or overrides: Caches should be auto-configured to use Memcache but
> config should be ignored/omitted since it's not used.

MediaWiki's PHP memcache class doesn't work, you have to use the PECL version,
but that was extremely simple:

$wgObjectCaches[CACHE_MEMCACHED] = array( 'class' => 'MemcachedPeclBagOStuff'
);

GAE automatically discards any configuration you try to give it, so nothing
needs to be done for that.

Note that when using Memcached though, you'll get hit with
https://code.google.com/p/googleappengine/issues/detail?id=10775.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
_______________________________________________
Wikibugs-l mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l

Reply via email to