On Friday, March 14, 2014 6:03:15 AM UTC+1, gslender wrote:
>
> Thanks Thomas. Can you also explain how things operate for GAE when and if 
> I were to employ SuperDev mode
>

Heavily depends whether you're using GWT-RPC or not.
 

> - I thought there would be no impact as the GWT module is loaded by 
> redirecting the HTML script to the compiler web server, but when I looked 
> at this before I ran into some issues where the "ip address" serving the 
> hosted page (in GAE) needed to match the compiler server (SuperDev Mode) 
> and until I was using the same "localhost" it wouldn't work.
>

Yes, this is a security measure added in 2.6.0. It's a bit hidden in the 
release notes:

   - 
   
   Security: with 2.6 we believe it's safe to turn on the Super Dev Mode 
   hook and leave it on in production. As an extra precaution, we recommend 
   setting the devModeUrlWhitelistRegexp configuration property to ensure that 
   it can only load JavaScript from localhost and your developers' machines in 
   your own domain.
   
 

> Do you know if much sociability testing between 2.6 and GAE is occurring?
>

I don't think so; from our part at least. We do try to at least try the 
samples before doing a (non-bugfix) release but that's all.
There's a reason for doing release candidates: crowd-sourcing the testing! 
;-)
 

> If I run into issues should I post them with GAE or GWT? Who would be 
> best/fastest to address them?
>

If you run into issues with GWT, then post in the GWT users 
group https://groups.google.com/d/forum/google-web-toolkit (or issue 
tracker if you believe it's a bug)
If we determine this is due to GAE, then you could post/report there.
Of course, if it's obvious that it comes from using GAE, then go directly 
to GAE groups/issue trackers ;-)

-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors
--- 
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].
For more options, visit https://groups.google.com/d/optout.

Reply via email to