[Server] create stack trouble

Jan Schenkel janschenkel at yahoo.com
Sun Aug 7 10:26:14 EDT 2011

I couldn't help but wonder why you wanted to save stacks from LiveCode Server.
The important part of this support is the ability to share business logic between desktop, mobile and server applications.

Storing data is an enticing idea, but flawed: stacks are not a multi-user data storage infrastructure.
Invocations of your .lc script from multiple clients may come in any order, and some processing may take longer.
And what if a user is impatient, hits the back button in his browser and pushes the same data again?

Stick with databases for storage, especially in multi-user scenarios - it's what the things were built for :-)

Jan Schenkel.
Quartam Reports & PDF Library for LiveCode

"As we grow older, we grow both wiser and more foolish at the same time."  (La Rochefoucauld)

----- Original Message -----
From: Martin Koob <mkoob at rogers.com>
To: use-revolution at lists.runrev.com
Sent: Sunday, August 7, 2011 3:15 PM
Subject: Re: [Server] create stack trouble

I have added an enhancement request to the QCC to have 'save stack'
implemented on LiveCode Server, Report #9664

Is there another way to save a stack that I am missing?

Is there a reason why allowing LiveCode server to save stacks would not be a
good idea?

I see it could be a way to store data without having to use a database. 
Poking around with stacks in LiveCode server has reminded me of starting out
with Hypercard and realizing how it could be used to store and categorize
information using stacks, substacks and cards.  However if you can't save
the stacks you have to store the data  in a database and  each time a page
is loaded recreate the set of stacks and cards.

View this message in context: http://runtime-revolution.278305.n4.nabble.com/Server-create-stack-trouble-tp3721781p3724846.html
Sent from the Revolution - User mailing list archive at Nabble.com.

use-livecode mailing list
use-livecode at lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:

More information about the Use-livecode mailing list