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

Jeff Massung massung at gmail.com
Wed Aug 4 17:07:52 CDT 2010


This is a typical, safe setup:

1. Client web browser clicks a button on a web page.
2. Web server sends a command to a CGI script (running on the server).
3. CGI script makes a connection to the database and runs a SQL function.
4. The SQL function executes a transaction on the database.

#1 is executed at some random, remote, external machine.
#2 is the only socket action that actually takes place.
#3 is run through the localhost loopback device to gain DB access.
#4 is entirely done within the database server code.

Something you can usually do as a quick test is to set your database up so
that it only accepts connections from the localhost. Then run through all
your tests. If any of them fail, that's a point where you are trying to
access the database remotely and need to fix it.

HTH,

Jeff M.



More information about the use-livecode mailing list