<div dir="ltr">Hi,<br><div class="gmail_extra"><br><div class="gmail_quote">2015-03-18 13:52 GMT+01:00 Christian Kuhn <span dir="ltr"><<a href="mailto:lolli@schwarzbu.ch" target="_blank">lolli@schwarzbu.ch</a>></span>:<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Including realurl now means:<br>
* Having something that works from day 1 of a core release<br></blockquote><div><br></div><div>It already does and even independent from core releases. I don't see the point in moving realurl to the core here.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
* If something else is developed or a path is laid, there will be some kind of migration path towards this - supported by core.<br></blockquote><div><br></div><div>If realurl never was part of the core, no migration is necessary. Old code will have to be rewritten in any case and new code</div><div>can just use the new solution. If the time comes, Dmitry or some else may create a migration from realurl to <fabulous-routing></div><div>but this is nothing that absolute has to be done and supported by the core.</div><div><br></div><div><br></div><div>Regards, Mathias</div></div></div></div>