Ahhh... sigh. :) I was hoping to avoid doing that. It certainly adds a layer of complexity that I was hoping to avoid.
On Oct 2, 10:49 am, "José Oliver Segura" <[EMAIL PROTECTED]> wrote: > 2008/10/2 Tony Arkles <[EMAIL PROTECTED]>: > > > > > I don't think that'll help. :( > > > I'm trying to ensure uniqueness... so if two people try to add the > > same URL, there will only be one entry in the datastore. I don't > > think there's any guarantee that tinyurl/etc would provide that > > uniqueness constraint. > > > Also, there will be a pretty decent volume of lookups going on, and > > routing every request through tinyurl won't win me any friends :) > > Then I think your only solution is to do it yourself (the > "tinyurl" service), assuring uniqueness. Basically, you "only" need to > mix datastore simple Gets with hashtable behaviour (taking care and > assuming that two different urls, despite rare, can result in the same > hash key). You need to query by hash key and then, among the results, > look for the matching url. Most of the time (depending on the url->key > algorithm) you should get few results, so overhead won't be a problem. > > Best, > Jose --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
