'page impression' techniques for banner ads
1999
It keeps the original formatting.
interpreted = N
texte = I can create a 'click-thru' banner ad system that makes it easy for non-webdna types to *correctly* place their own [include] tags (for banner positioning) into their own templates. Since an include tag is very easy for a non-webdna person to use, I am considering the following technique for a particular client:First, I allow the client to put tags like [include banner1] into his templates wherever he wants his banner ads to be displayed. If I use this technique, it means I will have several options for the webdna code snippet inside the banner1 file itself:Snippet Option #1:
[replace db=bannerads.db&eqbannerNamedatarq=banner1]bannerTotal=[math][bannerTotal]+1[/math][/replace]Snippet Option #2: [appendfile banner1Total]1[/appendfile]Snippet Option #3: [writefile banner1Total][math][include banner1Total]+1[/math][/writefile] My Theories:#1 would be fastest because it uses a database to calculate and store the total page impressions. If replacing a database field value is always faster than writing that value to a separate text file, this would seem to be the fastest solution -- because it does not require a disk hit.#2 would be second-fastest because all it does is append a single character to the end of a separate text file -- no additional [include]s, and no [math] to perform ...#3 would be slowest because it must include the value of a separate text file, then perform a math calculations on that value, then re-write the results to the separate text file. Question to PCS:Do you agree that I have shown these three snippets in the proper order from FASTEST to SLOWEST executing? If not, what order would you place them in? I'm not asking for a hard and fast answer here, all I'm seeking is your 'gut feeling' based on the fact that you're the ones who wrote the software ... :)My goal is to create a system that will perform as fast as possible, or at least as fast as NECESSARY -- and not get bogged down when there's a heavy load on the server. It seems the more repetitive disk hits there are, the slower it will perform, thus if DISK HITS are the limiting factor, I prefer to avoid them whenever possible ...Sincerely, Ken Grome 808-737-6499 WebDNA Solutions mailto:ken@webdna.net http://www.webdna.net
Associated Messages, from the most recent to the oldest:[include] tags (for banner positioning) into their own templates. Since an include tag is very easy for a non-webdna person to use, I am considering the following technique for a particular client:First, I allow the client to put tags like [include banner1] into his templates wherever he wants his banner ads to be displayed. If I use this technique, it means I will have several options for the webdna code snippet inside the banner1 file itself:Snippet Option #1:
[replace db=bannerads.db&eqbannerNamedatarq=banner1]bannerTotal=[math][bannerTotal]+1[/math][/replace]Snippet Option #2: [appendfile banner1Total]1[/appendfile]Snippet Option #3: [writefile banner1Total][math][include banner1Total]+1[/math][/writefile] My Theories:#1 would be fastest because it uses a database to calculate and store the total page impressions. If replacing a database field value is always faster than writing that value to a separate text file, this would seem to be the fastest solution -- because it does not require a disk hit.#2 would be second-fastest because all it does is append a single character to the end of a separate text file -- no additional [include]s, and no [math] to perform ...#3 would be slowest because it must include the value of a separate text file, then perform a math calculations on that value, then re-write the results to the separate text file. Question to PCS:Do you agree that I have shown these three snippets in the proper order from FASTEST to SLOWEST executing? If not, what order would you place them in? I'm not asking for a hard and fast answer here, all I'm seeking is your 'gut feeling' based on the fact that you're the ones who wrote the software ... :)My goal is to create a system that will perform as fast as possible, or at least as fast as NECESSARY -- and not get bogged down when there's a heavy load on the server. It seems the more repetitive disk hits there are, the slower it will perform, thus if DISK HITS are the limiting factor, I prefer to avoid them whenever possible ...Sincerely, Ken Grome 808-737-6499 WebDNA Solutions mailto:ken@webdna.net http://www.webdna.net
Kenneth Grome DOWNLOAD WEBDNA NOW!
Top Articles:
Talk ListThe 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...