On 18.05.2015 at 21:11 Uhr -0600 Mike Bonner apparently wrote:
With lc server, to do the "resident" thing, session control should work,
storing current data to the session variables which can then be used in
further calls (server side) This way you don't have to send the same
repeating data to the server every time, you can pull what you need from
the local server session and use it in your .lc scripts.
If I'm completely misunderstanding what you wish to do, of course ignore
this.
Session-specific data is not an issue. The concern is not sending the
data to the server. That comes in small chunks only. The concern is
the data that the server needs to display the pages for users. That
data transcends the sessions, meaning that it is the same for all
users, although different users use different subsets of that data.
In my current setup, I fetch that data into global arrays when
loading the program. By keeping that data resident, I reduce the
number of calls to the database by half and in some cases up to 75%.
That setup is quite old, however, and I want to upgrade it. Maybe
calls to the database are not as expensive on newer systems and
nothing to worry about.
RObert
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
