> It would be a titanic effort to rebuild so many standars. Would it? It been done many times before. And in the long run, I'm really only talking about (relatively) minor changes to the existing protocols. And then the "browser" sitting on top would just need to address security, and understand any languages it supported. By security, I mostly mean controlling what parts of the client computer can be accessed, changed, etc. I see the client side part of this being held in a sort of sand box on the client computer.
Thanks for the input. You make good points. Things to consider. If you haven't already, take a look at the html5 recommendations. I personally, still think there's a better way. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
