A few notes offhand:
On a slow connection pulling down multiple sections in one blob is tricky
-- JSON decoders don't normally stream so we end up being pretty slow with
that "second section and beyond" request.
I would love to be able to include action=query stuff along with a mobile
view request, such as grabbing the current user and site metadata.
Handling reference popups is dependent on loading the refs section, which
appears somewhere near the end. See above about slow connections. Could we
preextract them and ship them with the first section as metadata?
There are some oddities with remote file pages not returning a mod
timestamp.
Exposing CSS and scripting modules for extensions used would be nice.
Alternately we can try to retool things intoself contained embeddable I
frames.
-- brion
On Jul 25, 2014 4:26 PM, "Max Semenik" <maxsem.wiki(a)gmail.com> wrote:
Now that we have new shiny native apps and at the same
time we're about to
deprecate dynamic page views, it might be a good time to think for a while
about the API module that powers it, action=mobileview.
Having been written using assumptions about workflow that didn't come
true, it has accumulated some cruft and technical debt. I therefore propose
to form a long-term vision. I'd like to hear your thoughts on how it can be
changed, can its interface be simplified (e.g. [1]), how fast do we want it
to perform, what do we expect from Parsoid migration.
---------
[1]
https://bugzilla.wikimedia.org/show_bug.cgi?id=60485
--
Best regards,
Max Semenik ([[User:MaxSem]])
_______________________________________________
Mobile-l mailing list
Mobile-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l