Hi Shooter, The only way around this is if bit.ly/tinyurl/etc provide a 'bulk dereference' API. Without that, your only option is to do one URLFetch per URL. Note that you can use the asynchronous URLFetch support to parallelize this, though.
-Nick Johnson On Fri, Jul 10, 2009 at 2:15 AM, Shooter<manpree...@gmail.com> wrote: > > Hi guys, > > I am writing an application where I handle a lot of URLs - maybe 100s > for each user request, many of them are shortened by a service like > bit.ly or tinyurl. To dereference/expand these URLs, I have to do an > http get on that url and handle the http code 301 - which basically > means "redirected". That's how I get the real URL behind it. But that > consumes one URL fetch. So this means potentially 100s of URL fetches > per user request and that will easily hit the URL fetch limits if > people really start using this. > > Can someone suggest a way around this bottleneck? > > Thanks for your help. > > > > -- Nick Johnson, App Engine Developer Programs Engineer Google Ireland Ltd. :: Registered in Dublin, Ireland, Registration Number: 368047 --~--~---------~--~----~------------~-------~--~----~ 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 google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
