How safe and feasable is it ?

[Peter Haworth]

Don't think you can set the script of a running app. Maybe put all the
handlers into a separate library stack, password protected, and when your
main app detects an update it stops using the library stack, installs the
update, then starts using it again.

Pete
lcSQL Software
On Nov 7, 2014 12:33 PM, <jbv at souslelogo.com> wrote:

> Hi list
>
> Here's something I've had in mind for quite some time.
> Let's say you have an app built with LC that you send to
> various users as standalones with regular updates.
> What if all the most important functions of that app were
> gathered as handlers in the main stack script for instance, and
> at every startup, a script would check with a remote server
> for a possible update of that script, and dowload the new
> version (if any) to replace the old one with a simple
> "set script of this stack to myVar" ?
> The standalone could be a simple front end with all the
> most important objects, and therefore would weight slightly
> less than the complete app, and above all would need to
> be downloaded only once by end users who would not have
> to worry about versions and updates.
> At first glance this looks like a convenient way to update
> existing functions, add new ones, manage different settings
> among users, etc.
> But what about safety ? Is there a way to encrypt the main
> script while it is downloaded at startup so that it can't be
> caught by some sniffer ? And is there any other crucial
> security issue that didn't cross my mind ?
>
> Thanks
> 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
>