I also have the same problem. I remember asking about it a while ago and was told that it was a known shortcoming. I forgot to log it at the time as a defect. If you log it, I'm definitely interested and will star it.
j On Jul 28, 10:43 am, Ben Nevile <ben.nev...@gmail.com> wrote: > Hi, > > I have an app where users create an account, and then can access the > service throughwww.mywebsite.com/account_id. Awesome! But not so > awesome for the Current Load table that's on my dashboard, since > having the account_id as part of the URI and not a parameter means > that it doesn't aggregate stats in a meaningful way. No one URI has > much of a meaningful load, even though something like /.*/settings > might account for 50% of all the requests. > > Am I stupid to be structuring my URIs this way? It seems reasonable > to me. It would be boss if this URI table was based on the mappings > we declare in our app. > > Ben --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
