On 11.02.2013, 22:11 Asher wrote:
And then I'd wonder about the server side
implementation. How will frontend
cache invalidation work? Are we going to need to purge every individual
article section relative to /w/api.php on edit?
Since the API doesn't require pretty URLs, we could simply append the
current revision ID to the mobileview URLs.
Article HTML in memcached
(parser cache), mobile processed HTML in memcached.. Now individual
sections in memcached? If so, should we calculate memcached space needs for
article text as 3x the current parser cache utilization? More memcached
usage is great, not asking to dissuade its use but because its better to
capacity plan than to react.
action=mobileview caches pages only in full and serves
only sections requested, so no changes in request patterns will result
in increased memcached usage.
--
Best regards,
Max Semenik ([[User:MaxSem]])