Commercial Indy License for HTML5

[Kevin Miller]

You¹ll always have a choice how much code to put on the server side and in
the client. Our HTML5 output operates on your stack within the client
browser, like a standalone does now. However you can still connect to a
web service or LC server in the same way you do today. Keeping key
portions of code there could be used to aid security.

Almost everything computing can be reverse engineered and hacked with
enough effort. You can reverse engineer a complied app, or dig around in a
debugger. That doesn¹t make it easy, doesn¹t make it practical, doesn¹t
necessarily give you source code that is editable, nor give you any rights
to use it.

Kind regards,

Kevin

Kevin Miller ~ kevin at livecode.com ~ http://www.livecode.com/
LiveCode: Everyone can code




On 20/07/2014 12:46, "jbv at souslelogo.com" <jbv at souslelogo.com> wrote:

>Hi list,
>I've been following this thread and was wondering :
>please correct me if I'm mistaken, but we'll still be in a
>client/server configuration, so keeping the important code server-side
>could be a way to avoid people hacking/stealing your app...
>Sure, dealing with client/server requests will require more coding and
>expertise than simply compiling a stack in html5 and viewing it in a
>browser, but in critical situations it might be a workaround...
>
>And nevertheless it will be an easier task than coding the server side
>in LC and the client side in js/html as many of us have been doing for
>a while, since everything will be coded with LC...
>And although this is not my field of expertise, according to the few
>google searches I've done, it looks like js obfuscation can always be
>reverse engineered, so...
>
>Best
>jbv
>
>
>_______________________________________________
>use-livecode mailing list
>use-livecode at lists.runrev.com
>Please visit this url to subscribe, unsubscribe and manage your
>subscription preferences:
>http://lists.runrev.com/mailman/listinfo/use-livecode