Nevermind you answered my question above.
--
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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To
I find most of our customer base uses GWT RPC. The story on using this may
make using gwt feel complicated.
If we can just compile into the web app directory for the entire process,
then there would be no need for a proxy. From what I could tell it would be
3 args, -war, -browser (or maybe
I am seeing a lot of arguments pop up about GWT RPC, but I think it should
not be considered for this discussion at all. In my mind GWT 2.8 will be
the last release that has GWT RPC and people should start migrating. I
think its perfectly fine do design a replacement to devmode without GWT RPC
Well it is just what I would ask for in order to replace local apache /
nginx on developer machines with GWT devserver. It's not a problem to
simply continue using a dedicated proxy either with CodeServer or a "no-op"
devserver.
Basically our setup is more a less the result of two decisions:
On Monday, October 24, 2016 at 11:23:07 AM UTC+2, Jens wrote:
>
> Hmm generally I like having build-in proxy with GWT, as I usually use a
> proxy anyways at work just to mimic the production behavior (load balancers
> serving static GWT app files and proxy certain requests to servlet
>
On Monday, October 24, 2016 at 3:55:47 AM UTC+2, Brandon Donnelson wrote:
>
> I like the sounds on this, although my initial thoughts feel like it's
> another layer. But I also know typically it takes me a bit longer to warm
> up to new approaches. I have trying to think how I can cut the code
I like the sounds on this, although my initial thoughts feel like it's
another layer. But I also know typically it takes me a bit longer to warm
up to new approaches. I have trying to think how I can cut the code server
out of the loop.
So I've been wondering if I could start the gwt super
