Re: Updating a database once per day - An example

This WebDNA talk-list message is from

1998

It keeps the original formatting. numero = 17969
interpreted = N
texte = On 5/30/1998 11:58 pm, Kenneth Grome so noted...>>>Okay, so what you must do is put that newly-created db into a *different*>>>folder than the file it's replacing. Then when you write your WebDNA code,>>>you can do all the tasks above, all in a single template. This is very>>>important, because you must make sure that after WebCatalog closes the>>>current db, another request does NOT open it again before WebCat has>>>replaced it.>>>>Just to make sure I have this correct before implementing site-wide (I've>>been pondering this same problem for the past week as well)...>>>>As long as all these operations happen in a single template, there's no>>chance of another page trying to get at the database while it's in>>limbo? No matter how many threads the webserver's running or how many>>hits per second, when you get right down to the nitty gritty it's only>>possible for WebCatalog to be handling a single task at once?>>No, it performs multi-threading tasks very easily most of the time, >because anything that's not purging the data from RAM can always be >performed simultaneously. But when you're closing a database, it has to >wait for the *other* threads to finish what they've started with that db, >then it closes the db ...Okay, so if my template closes a database on a busy server, then [movefile]s in a newly uploaded copy of the database, it's possible for WebCatalog to reopen this database between the closing and the file transfer if it receives another request for it?Rob MarquardtDesigner/Resident WireheadToast Design300 First Avenue North, Suite 150Minneapolis MN 55401612.330.9863 v612.321.9424 fwww.toastdesign.com Associated Messages, from the most recent to the oldest:

On 5/30/1998 11:58 pm, Kenneth Grome so noted...>>>Okay, so what you must do is put that newly-created db into a *different*>>>folder than the file it's replacing. Then when you write your WebDNA code,>>>you can do all the tasks above, all in a single template. This is very>>>important, because you must make sure that after WebCatalog closes the>>>current db, another request does NOT open it again before WebCat has>>>replaced it.>>>>Just to make sure I have this correct before implementing site-wide (I've>>been pondering this same problem for the past week as well)...>>>>As long as all these operations happen in a single template, there's no>>chance of another page trying to get at the database while it's in>>limbo? No matter how many threads the webserver's running or how many>>hits per second, when you get right down to the nitty gritty it's only>>possible for WebCatalog to be handling a single task at once?>>No, it performs multi-threading tasks very easily most of the time, >because anything that's not purging the data from RAM can always be >performed simultaneously. But when you're closing a database, it has to >wait for the *other* threads to finish what they've started with that db, >then it closes the db ...Okay, so if my template closes a database on a busy server, then [movefile]s in a newly uploaded copy of the database, it's possible for WebCatalog to reopen this database between the closing and the file transfer if it receives another request for it?Rob MarquardtDesigner/Resident WireheadToast Design300 First Avenue North, Suite 150Minneapolis MN 55401612.330.9863 v612.321.9424 fwww.toastdesign.com Rob Marquardt

DOWNLOAD WEBDNA NOW!

Re: Updating a database once per day - An example

1998

Top Articles:

Related Readings: