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 :)


On Oct 2, 10:34 am, Gmail <[EMAIL PROTECTED]> wrote:
> Maybe,You Can try to short the URI by some service like this one;
>
> > Short URL is a Wordpress plugin that allows you to take a long URL  
> > such as:
>
> >http://www.harleyquine.com/downloads/php-scripts/somefile.zip
>
> > and turn it into:
> >http://www.harleyquine.com/u/1
>
> there are lots of this kind of services.
>
> 在 2008-10-2,下午11:55, Tony Arkles 写道:
>
>
>
> > Hi everyone,
>
> > I'm running into a bit of a snag, and I'm hoping that someone might be
> > able to offer some suggestions.
>
> > I've got a Kind that is keeping track of information about URLs
> > (ratings, summary, etc).  At first glance, it seems natural to key
> > Entities based on the full URL -- this will ensure that there is only
> > ever one entry for each URL.  get_or_insert() works awesome for this.
>
> > This design was working great until yesterday, when I hit a URL that
> > was longer than 500 characters (egads!).
>
> > Now I don't know what to do!  I want to ensure uniqueness on a per-URL
> > basis, but it doesn't look like I can use it as a key anymore.  Since
> > you can't do queries within transactions, I'm at a loss for how to do
> > this...
>
> > Any thoughts?
>
> > Cheers
> > Tony
>
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google App Engine" 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/google-appengine?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to