numero = 60701
interpreted = N
texte = I've created a banner rotating system and have noticed that random isn't = so random just like many people have on the talk-list. After reading the= talk-list e-mail database it seemed like using "allhit=3D1" was the solu= tion so I tried it and it didn't work for me. Here's my search string: [search db=3Dtest.db&neskudatarq=3D[blank]&skusort=3D1&skusdir=3Dra&skuty= pe=3Dnum&max=3D1&allhit=3D1] It's crucial to my banner system that the banners reach a certain amount = of views in a month's time. One way we thought to fix this is by taking = the banners that have reached their quota for the month and turn them off= so that the other banners can catch up. This won't be efficient in the = future when the volume of banners running increases. We don't need a sys= tem that must show every banner and keeps track of that (we would use a t= emporary db to do that) we just need a random that has a less dramatic be= ll curve. And we don't want to recode part of our system based on poor r= andom performance. Have there been any new discoveries with WebDNA's random function? What = are other people doing to get around this problem? Has SM said anything = to anyone? Thanks. Justin Carroll ------------------------------------------------------------- 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:
I've created a banner rotating system and have noticed that random isn't = so random just like many people have on the talk-list. After reading the= talk-list e-mail database it seemed like using "allhit=3D1" was the solu= tion so I tried it and it didn't work for me. Here's my search string: [search db=3Dtest.db&neskudatarq=3D[blank]&skusort=3D1&skusdir=3Dra&skuty= pe=3Dnum&max=3D1&allhit=3D1] It's crucial to my banner system that the banners reach a certain amount = of views in a month's time. One way we thought to fix this is by taking = the banners that have reached their quota for the month and turn them off= so that the other banners can catch up. This won't be efficient in the = future when the volume of banners running increases. We don't need a sys= tem that must show every banner and keeps track of that (we would use a t= emporary db to do that) we just need a random that has a less dramatic be= ll curve. And we don't want to recode part of our system based on poor r= andom performance. Have there been any new discoveries with WebDNA's random function? What = are other people doing to get around this problem? Has SM said anything = to anyone? Thanks. Justin Carroll ------------------------------------------------------------- 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/
"Justin Carroll"
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...