On Sun, Dec 6, 2009 at 7:09 PM, Gregory Maxwell <[email protected]> wrote: > hm. This could be resolved by mixing in the URL stuffing alternative, > linking to /target#from_redirectname then letting client side JS code > generate the redirect back-link.
Except if there's already a fragment in the link. And it wouldn't help browser link coloring. And of course wouldn't work without JS (not prohibitive, but a disadvantage). You could add a query parameter, but at that point it's an entirely different URL anyway, so not much point. > ...but workqueue workload is why I waved my arms about request merging and > priority queueing. I'd expect that the actual additional work in fixing up > redirect destination changes would be pretty negligible if the entries > were handled at a lower priority and eliminated whenever their task > was completed as a side effect of some other change. They'd also never get done if the job queue is always overloaded with higher-priority tasks. _______________________________________________ Wikitech-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikitech-l
