[RevServer tips] Spreading the load or why wise developers use asynchronous workflows

Andre Garzia andre at andregarzia.com
Wed Aug 4 17:27:19 EDT 2010


Let me tell you that I once did something like that by accident on my own
test server. I had a recursive process that started spawning itself and
would not quit... in the end I had to reboot the damn vps. Thats why those
limits are important


On Wed, Aug 4, 2010 at 6:23 PM, Chipp Walters <chipp at chipp.com> wrote:

> Brilliant example, Bob! Thanks so much for sharing.
> On Wednesday, August 4, 2010, Bob Sneidar <bobs at twft.com> wrote:
> > Okay, so let's say I'm a script kiddie with a bug up my butt about your
> web server. I decide I am going to take it down. Now I'm smart enough to
> know that servers are multi-threaded, meaning they can host lots of
> connections and process threads to manage simultaneous connections. But what
> I am banking on is that your server does not have any limits on how long a
> process can stay <snip>
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution

http://www.andregarzia.com All We Do Is Code.

More information about the Use-livecode mailing list