LiveCode server single-thread risks and considerations?

[stephen barncard]

I have a good server tip, recommended by Andre:

*break things into small processes rather than large crunching routines, use
small chunks at at time to give breathing room for other processes.*
*
*
As far as security, Livecode should be at least as secure as PHP.  All
traces of the code are gone by display time.


On 1 August 2011 10:48, Keith Clarke <keith.clarke at clarkeandclarke.co.uk>wrote:

> Hi folks,
> Now that we have a released LiveCode server - and a few experts have
> climbed the burning rope for mere mortals to follow - I'm about to dive into
> the LC server goodies my on-rev service. However, I have a sense-check
> question to the early-adopter community...
>
> What are the top-3 (or 5 or 10) risks/gotchas that we need to consider with
> LiveCode Server's single-threaded architecture - and how do we mitigate
> these in the somewhat 'exposed-to-nastiness' world of servers?
>
> Is there a LiveCode server dos and don'ts list somewhere?
> Best,
> Keith..
> _______________________________________________
> 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
>



-- 



Stephen Barncard
San Francisco Ca. USA

more about sqb  <http://www.google.com/profiles/sbarncar>