Yes, this is correct, and this is why more and more people want better IP protection for client-side browser code. Unfortunately it just isn't possible with modern browsers, hopefully one day it will be.
On Mon, Nov 7, 2011 at 9:35 AM, Uemit <[email protected]> wrote: > @Palo G. > Actually I wasn't suggesting to protect the generated javascript but to > put the algorithm on the server/backend and access it from the client via > RPC or any other method. > I think what OrNot wanted to know is whether he can somehow make sure that > only specific user can execute the RPC call and this can be done if the RPC > is secured via some authentication/authorization mechanism. > I also agree security by obscurity is not the right approach. > > However I do believe there is a use case for time consuming computations > on the client side. With each browser iteration/version Javascript Engine > becomes faster and faster and nowadays a common desktop machine/laptop has > enough horse power to do computational intense calculations on the client > side. So I think more and more some computational tasks which used to be > done on the backend will move to the client. > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-web-toolkit/-/c83YRnzgjYcJ. > > 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. > -- Harpal Grover President *Harpal Grover Consulting Inc* -- 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.
