If it's faster, go for it, don't see how it can break hosted mode.
If a substantial amount of the hosted start-up time is actually the
server, one alternative might be to have a built-in way to start up
the server portion separately, and let it stay running while iterating
client code. I find the server code to generally be more amenable to
hot-swapping, while changes in client code often require a restart, so
if it didn't have to restart the server each time that would be a big
bonus. Of course I can currently set stuff up run the server
separately on my own, but having the ability built-in seems more along
the GWT philosophy of easy entry.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~----------~----~----~----~------~----~------~--~---
