From: Chris H. <cha...@ch...> - 2008-06-27 12:33:31
|
[adjusted the subject to create a new thread] Bharat... Further to your suggestion #4 below, this would be ideal, within the issues you've described. I made a similar but slightly different suggestion on the forums, which I'll copy here. I don't know which of the two would be the easiest to implement -- I defer to you all. Thanks. -Chris " 4. Provide a means of specifying an offset for global functions. This could actually be semi-automated with the ProcessBar display -- using the JavaScript onload() function. The processing script could provide information to the page as to what point it has last checkpointed (read: committed to the file store / database). If onload executes, and this number is less than the total, then the page could display a "Did not complete... Continue the process" link which would effectively leverage on the offset function. On Thu, Jun 26, 2008 at 17:04, Bharat Mediratta <bh...@me...> wrote: > 4. As we go through the process of rebuilding derivatives, we keep counters > in the database with the ids of the item that we've checked. One counter is > the largest (most recent) derivative id when the run started, the second > counter is the smallest (oldest) derivative id > that we got to on prior runs. These counters define a window. When we do > the next run, we check any derivatives outside of the window and move the > counters towards the edges as appropriate (ie: we widen the window). > > Solution #4 has the upside of making it so that we can run this task over > and over again. It has the downside that if something goes wrong on an > image rebuild, you can't get it to try rebuilding that image again easily > because its id will be inside the window. > -- Chris Halsall ( cha...@id... ) Ideas 4 Lease (Barbados) www.ideas4lease.com Paynes Bay, St. James, BB 24023 246. 256. 1024 (O) 246. 432. 5381 (F) |