Proxying wasn't an option for developers because of the I.T. security protocols. Besides it feels a bit overcomplicated to have to set up a channel back to the code server. I think it would be easier to clobber the codeserver api with a workaround and setting the hosteName and hand that to the developers. I'm contemplating on forking the code server for GWT 2.7 users to provide a workaround for the hostName through the program arguments.
On Sat, Sep 10, 2016 at 1:43 AM Thomas Broyer <[email protected]> wrote: > How about proxying through a local server that would intercept the > nocache.js and route everything else to your external server? This is > basically how webpack devserver and browserSync work in the JS land. > > -- > 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/13bfb1ba-f2fb-40cf-afda-c9902d016cb3%40googlegroups.com > . > For more options, visit https://groups.google.com/d/optout. > -- *Brandon Donnelson* GXT Support Engineer <http://www.facebook.com/senchainc> <http://twitter.com/sencha> <https://www.linkedin.com/company/sencha-inc> <http://www.youtube.com/SenchaInc> <https://plus.google.com/117303203295549187007?prsrc=3> [image: SenchaCon 2016 Aria Resort, Las Vegas, November 7-9] <https://www.senchacon.com/> *Join me at SenchaCon 2016!* -- 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/CAA_mbNO97_gUCZiAPKOAG%2BNRG3pD0AWyt8wLrjFhSdGwSdioEA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
