| daniel added a comment. |
AFAIK we do have infrastructure for running node servers with proper caching, as part of the rest services layer.
If you create endpoints that return structured data you could consume those from the PHP backend or the JS client.
We have node based rendering infrastructure, but as far as I know, we cannot use them to directly serve page views. Because a) all the skin/chrome stuff is done in PHP and b) we currently only use node when editing, and don't have the server capacity to handle several orders of magnitude more hits that would be needed for serving page views.
So, we can use node.js to render stuff, but we still need to loop it through PHP to add chrome. We also need caching for this on the same level as the parser cache. That could be done on the HTTP level between PHP and node. Does this exist?
I still think that this kind of thing is viable right now only for an editing interface. For full page views, this needs more work, see T111588: RFC: API-driven web front-end.
Cc: GWicke, Aleksey_WMDE, daniel, Niedzielski, Magnus, Milimetric, Prtksxna, Fjalapeno, phuedx, Jdlrobson, siddharth11, Capt_Swing, TheDJ, Jdforrester-WMF, SBisson, WMDE-leszek, Volker_E, Krinkle, gabriel-wmde, Jonas, thiemowmde, Lydia_Pintscher, Jan_Dittrich, Jhernandez, Jdrewniak, Aklapper, QZanden, Salgo60, SamanthaNguyen, JGirault, Izno, Wikidata-bugs, aude, Mbch331, Jay8g
_______________________________________________ Wikidata-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
