Ok, I'll be publishing it here: https://github.com/rdwallis/gwt-pushstate probably early next week.
On Fri, Oct 3, 2014 at 6:53 PM, confile <[email protected]> wrote: > @Richard Wallis Could you please publish your updated pushstate > implementation? > > Thank you > Michael > > Am Freitag, 3. Oktober 2014 18:51:51 UTC+2 schrieb Richard Wallis: >> >> Ok the Historian interface looks like it will solve our issues. I'll >> rewrite GWTP's PlaceManagerImpl to use it and update my pushstate >> implementation. >> >> On Fri, Oct 3, 2014 at 6:34 PM, Thomas Broyer <[email protected]> wrote: >> >>> >>> >>> On Friday, October 3, 2014 4:06:01 PM UTC+2, Manuel Carrasco Moñino >>> wrote: >>>> >>>> There is no plans to upgrade Jetty. It implies some changes in >>>> JettyLauncher and WebServer, I have already a patch for that but not >>>> committed yet because I have not tested enough. If someone else demands it >>>> we could consider to upgrade it. >>>> >>> >>> AFAIK, we can't update Jetty to 9.x because HTMLUnit (used for >>> JUnitShell/GWTTestCase) depends on Jetty 8.x APIs (WebSockets) >>> There's been a patch proposed already and it has been abandoned because >>> of that. >>> >>> >>>> Anyway I think it should be nice not to bundle jetty in the .jar >>>> deployed in maven repos, but set it as a dependency so as it's easier to >>>> experiment other versions. >>>> >>> >>> It could possibly help with some setups but I doubt it'd be that useful. >>> >>> If we had a modularized GWT then you could avoid depending on gwt-junit, >>> gwt-devmode-jettylauncher and gwt-codeserver (e.g. when compiling) and live >>> with Jetty 9.x dependencies in your classpath/buildpath, or we could >>> possibly provide a gwt-codeserver and/or gwt-devmode-jettylauncher using >>> using Jetty 9.x; so you'd use Jetty 8.x with gwt-junit to run your >>> unittests, and you could use Jetty 9.x in DevMode/superDevMode (and benefit >>> from Jetty 9.x perf improvements for gwt-codeserver?) >>> It's not possible with our current monolithic artifacts (and build) >>> though. >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "GWT Contributors" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected] >>> . >>> To view this discussion on the web visit https://groups.google.com/d/ >>> msgid/google-web-toolkit-contributors/d22e2d8b-0bf1- >>> 4f17-9805-9fdb944076f5%40googlegroups.com >>> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/d22e2d8b-0bf1-4f17-9805-9fdb944076f5%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- > You received this message because you are subscribed to the Google Groups > "GWT Contributors" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/google-web-toolkit-contributors/2560e5b0-6f75-4580-b75b-435bd04296b1%40googlegroups.com > <https://groups.google.com/d/msgid/google-web-toolkit-contributors/2560e5b0-6f75-4580-b75b-435bd04296b1%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAEqaEVjcfPpgeg5uCOkz__TTFux8z2JVQpyN2eVCX_W%2BYfOaCA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
