@Palo,G: Uemit is correct. There are many cases that need client computing and specific algorithms, for instance, image processing, especially for those which need prompt interactivity. You can not always push the data to the sever to process and then get the result back to show. In low bandwidth internet, that will bring the user to kill himself.
At least till now, the GWT is commonly used for text-based applications, say ,information system. As the HTML5 comes into play, more and more canvas or webgl based web applications will be made by J.S.and most of them need intensive client computing.I believe the IP issue will become more and more important. Actually it is hard for me to understand why J.S., such a poor language, is becoming so popular. Sun,the stupid giant, made too many mistakes that let java , so great language, lose his position in internet era. In some sense, the GWT project is damn ironic,isn't? On Nov 8, 12:29 am, Uemit <uemit.se...@gmail.com> wrote: > @Harpal Grover: > Actually there might be a solution right now. You can use Native Client > SDK<http://code.google.com/chrome/nativeclient/>to develop a C++/C > application which runs in the browser. The application > will be compiled to a binary and then transmitted to the client/browser > where it is executed in a sandbox. It is still possible to use > a Dis-assembler in order to figure out the algorithm however it is much > harder than obfuscated javascript code. > However until now NaCl is only supported in Chrome. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
