Real-time stack updating

[Mark Schonewille]

Hi Richard,

How do you trigger the script that reads and displays the data? If  
you do that from a startup handler, it may bot work. If you have  
lockmessages set to true at some point and trigger the script from a  
(pre)openstack handler, it may not work.

Why don't you check for the update on startup, before opening the  
second stack, and download the update before reading the data? Just  
keep the entire updating process in stack one. This is faster and  
more secure because it will even work if the second stack contains a  
critical bug.

Best,

Mark

--

Economy-x-Talk
Consultancy and Software Engineering
http://economy-x-talk.com
http://www.salery.biz

Get your store on-line within minutes with Salery Web Store software.  
Download at http://www.salery.biz

Op 11-okt-2006, om 13:33 heeft Richard Miller het volgende geschreven:

> Here's the scenario.
>
> Stack 1 is a main stack that acts as a startup file. It's an .exe.
>
> Stack 1 opens a separate Stack 2 (a .rev stack). Stack 2 performs  
> all the main functionality of our program.
>
> Stack 2 checks our server (when it first starts up) to see if there  
> is a more recent version available for update. If so, it begins the  
> update process. At the end of the process, this stack shuts itself  
> down and starts up a sub-stack of Stack 1. Stack 2's properties  
> have the DestroyStack set to true. I'm not aware how any handler in  
> Stack 2 might still be running after it has issued the "close"  
> function to itself.
>
> Stack 1's "update file" substack does the following:
>
> 1. Deletes Stack 2
> 2. Downloads a new Stack 2
> 3. Starts new Stack 2
>
> The problem is that, when this new Stack 2 starts up, it does not  
> initially show the updated data. However, simply quitting it and  
> restarting it DOES now show the updated data.
>
> I'm not sure what more I need to do so that the first startup of  
> this new Stack 2 will show the updated data.
>
> Thanks.
> Richard Miller
> Imprinter Technologies