Re: Freeze
This WebDNA talk-list message is from 2003
It keeps the original formatting.
numero = 47642
interpreted = N
texte = >>Do I really have to download the entire webdna 4.5.1 package simply >>to read the change history? >> >>If not, then why isn't there a link to the change history in a >>prominent place in the developer resource center? > >The Change History is in the Command Reference Section-Appendix C >http://webdnadocs.smithmicro.com/WebDNA%20Change%20History.html Yes, it's in the section entitled WebDNA 4.5.1 Language Reference which is misleading but nevertheless it's in there. And here's what it says about this new feature:New 'Safe-Write' preference - Enabled by default. When enabled, the WebDNA engine creates a temporary file when writing the contents of a database to disk. The temporary file contents are then moved to the original database file after the entire database is completely flushed to disk. This helps to eliminate corruption of the original database file if there is an interruption during the database write process.In other words, instead of just writing the changes to RAM or to a single disk file, this new preference does the following:1- closes a db upon every append, replace and delete 2- writes a new temporary db file to disk 3- deletes the original db file 4- renames the temporary file to the original db file nameAnd of course since the original db file has been deleted and another file has taken its place, the new file is not yet open in webdna's RAM cache ... so it takes additional time for the new db file to be opened before any visitor can use it.And if the request that opens the closed db file is an append, replace or delete, the file will be immediately closed and replaced again -- thus eliminating all the benefits of RAM-caching of data.Clearly this takes a lot more time than the old way of writing to a db, especially with large db files and slow OS's ... Sincerely, Kenneth Grome--------------------------------------------------- WebDNA Professional Training and Development Center 175 J. Llorente Street +63 (32) 255-6921 Cebu City, Cebu 6000 kengrome@webdna.net Philippines http://www.webdna.net ---------------------------------------------------------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list
. To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Associated Messages, from the most recent to the oldest:
>>Do I really have to download the entire webdna 4.5.1 package simply >>to read the change history? >> >>If not, then why isn't there a link to the change history in a >>prominent place in the developer resource center? > >The Change History is in the Command Reference Section-Appendix C >http://webdnadocs.smithmicro.com/WebDNA%20Change%20History.html Yes, it's in the section entitled WebDNA 4.5.1 Language Reference which is misleading but nevertheless it's in there. And here's what it says about this new feature:New 'Safe-Write' preference - Enabled by default. When enabled, the WebDNA engine creates a temporary file when writing the contents of a database to disk. The temporary file contents are then moved to the original database file after the entire database is completely flushed to disk. This helps to eliminate corruption of the original database file if there is an interruption during the database write process.In other words, instead of just writing the changes to RAM or to a single disk file, this new preference does the following:1- closes a db upon every append, replace and delete 2- writes a new temporary db file to disk 3- deletes the original db file 4- renames the temporary file to the original db file nameAnd of course since the original db file has been deleted and another file has taken its place, the new file is not yet open in webdna's RAM cache ... so it takes additional time for the new db file to be opened before any visitor can use it.And if the request that opens the closed db file is an append, replace or delete, the file will be immediately closed and replaced again -- thus eliminating all the benefits of RAM-caching of data.Clearly this takes a lot more time than the old way of writing to a db, especially with large db files and slow OS's ... Sincerely, Kenneth Grome--------------------------------------------------- WebDNA Professional Training and Development Center 175 J. Llorente Street +63 (32) 255-6921 Cebu City, Cebu 6000 kengrome@webdna.net Philippines http://www.webdna.net ---------------------------------------------------------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Kenneth Grome
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
Protecting Images (2003)
replace using &append=T (2007)
Location of Browser Info.txt file (1997)
Probably a very simple question? (1997)
Another question (1997)
webcat pro (1998)
WCS Newbie question (1997)
SQL Error 22003 (2001)
autosensing lanague selection (1997)
[WebDNA] Migration from 6.2 to 7. Problems with writing to DB's (2012)
Forms Search Questions (1997)
Suggestions on best way to work with yyyy/mm/dd (1997)
IP Shows Server (2003)
[OT] will work for... (2003)
PCS Frames (1997)
SKU number. (2000)
Emailer problem with WC 2.1, NT, WebSite 2.1 (1998)
WebCatalog for Postcards ? (1997)
How to add product size choices to form? (1997)
[WebDNA] returnraw redirects on version 6.2.1 on CentOS (2013)