ok so i guess i could use one key 'whois' to serialize access to the whois database and then do caching of domain status using the domain name as key.
however, i've already run into the next problem: when i update beaker from the mercurial repo, pylons refuses to start... paster says: pkg_resources.DistributionNotFound: Not Found: brightside (did you run python setup.py develop?) (that name would be my web application, brightside). i am still using pylons 0.9.5 and paste 1.2.1. any ideas why updating beaker interacts with paste in this way? when i change back to the egg version, everything runs as expected. i understand i *should* be using the very newest version of beaker because of the bugs that were discussed in thread "beaker cache lookup error" recently on pylons-devel. _wolf On Feb 21, 10:44 pm, Ben Bangert <[EMAIL PROTECTED]> wrote: > On Feb 21, 2008, at 1:07 PM, wolf wrote: > > > thanks for your suggestion -- sounds reasonable. > > > what i don't get is: why do i have to devise a scheme to serialize > > accesses to the cache create function if beaker cache already > > "implements a a multiple-reader/single-writer locking > > system so that multiple threads/processes can read the data while it > > will only be made a single time" as you say? isn't that exactly what a > > locking system is supposed to do? why do it another time? > > Because that system ensures that Beaker isn't attempting to recreate > the *same* key at once. You don't want *any* keys to be created at the > same time, since you're limited to whois lookups. Beaker locks to > prevent multiple *same* key creations at once, my reading of your > particular issue that you only want a *single* whois query run at a > time regardless of which one it is (I'm assuming you're keying by name). > > Does that make sense? > > Cheers, > Ben > > smime.p7s > 3KDownload --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
