daniel closed this task as "Resolved". daniel added a comment. Quick summary of the investigation:
- mobile uses separate web cache keys, so no problem there. - mobile shares the parser cache with the desktop version - if we remove the blob from the cached ParserOutput for mobile, we need to split the parser cache. That may be doable, but isn't great, see https://phabricator.wikimedia.org/T125899. - it would be nicer to never put the serialized entity into the ParserCache, but add it on the fly when serving the editable (desktop) interface. - We'd need a mechanism for manipulating the ParserOutput when it gets pulled from the ParserCache. - We may want to cache the serialized blob separately (which means more fun with purging). - compare T106099: RFC: Page composition using service workers and server-side JS fall-back <https://phabricator.wikimedia.org/T106099> TASK DETAIL https://phabricator.wikimedia.org/T125391 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: daniel Cc: aude, Jdlrobson, daniel, Jonas, adrianheine, thiemowmde, Tobi_WMDE_SW, Aklapper, Izno, Wikidata-bugs, GWicke, Mbch331 _______________________________________________ Wikidata-bugs mailing list Wikidata-bugs@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
