On Fri, 08 Mar 2013 18:18:52 -0800, Waldir Pimenta waldir@email.com wrote:
On Wed, Feb 27, 2013 at 9:13 PM, Daniel Friesen daniel@nadir-seen-fire.comwrote:
I wouldn't even include mw-config in entrypoint modifications that would be applied to other entrypoint code.
You mean like this one https://gerrit.wikimedia.org/r/#/c/49208/? I can understand, in the sense that it gives people the wrong idea regarding its relationship with the other access points, but if the documentation is clear, I see no reason not to have mw-config/index.php benefit from changes when the touched code is the part common to all *entry* points (in the strict meaning of files that can be used to enter the wiki from a web browser).
No different changes. I was talking about this RFC: https://www.mediawiki.org/wiki/Requests_for_comment/Entrypoint_Routing_and_4...
Part of the plan was to move all the entrypoint handling into the common code. All the entrypoint files like api.php would become non-mandatory. They would basically be tiny files that all just include the MediaWiki code in the exact same way. While the common code does the work deciding what code to run for which entrypoint. After that most of the paths could be blindly directed right to index.php and the codebase would handle delegating paths like api.php to the Api, handling 404s, etc...
mw-config/index.php would never get that tweak.
--Waldir