Stacks delivered via the web?
troy at rpsystems.net
Mon Sep 16 20:29:01 CDT 2002
On Monday, September 16, 2002, at 09:10 PM, Judy Perry wrote:
> Could someone describe to me, on or off-list depending how much you
> anticipate everyone's gonna groan, just how the below works? I am not
> certain I am understanding it well enough to present it as a potential
> solution to the department...
I believe what is being described is a "stub" program. Essentially a
distributed version of the Rev engine which makes a call to a server to
receive the actual stack files to be run. In turn, that actual stack
file could be a menu which allows the selection of other stacks which
reside on the server. To update the "menu", one simply has to update the
menu stack which resides on the server. It basically acts as a program
which the creator does not have to decide what they want the program to
do when they distribute it. All that needs to be decided is where the
program will get its future instruction from (the server location and
This is exactly what I was referring to when I mentioned that forcing a
browser based solution was rather short sighted - after all, Director
requires the ShockWave plugin... isn't that about the same as a "stub"
More information about the use-livecode