On 8/5/07, Alex Nikolaenkov <[EMAIL PROTECTED]> wrote:
> Imagine that your site hosting photos has got the following urls
> belonging to different users:
> http://mysite.com/John/
> http://mysite.com/john.

Except those aren't different URLs. And now that I'm slightly more
awake I'm wondering why we're even having this debate:

http://www.b-list.org/weblog/categories/django
http://www.b-list.org/weblog/categories/Django

Django handles both just fine, returns the same page for both.

http://www.b-list.org/weblog/2007/06/25/hacking-comments-without-hacking-comments
http://www.b-list.org/weblog/2007/06/25/HACKING-COMMENTS-WITHOUT-HACKING-COMMENTS

Again, works just fine. Which says that case-sensitivity is not
something Django is imposing.

And again, I'll reiterate that the type of user who doesn't understand
case-sensitivity is the type of user who -- verified by repeated
real-world usability testing -- finds MySpace by going to Google and
typing "myspace.com" into the search box. An astonishingly high
percentage of web

> One got to the John's homepage and liked
> his photos very much. But suddenly his browser crashes and the only
> thing he remembers that he was at the "john's page at mysite.com". So
> he navigates to the location bar types "http://mysite.com/john"; and
> is redirected to some porno photos of his beloved cat. Confusing, isn't it?
> The case of the link is not a big deal for the end user. Do you feel
> the difference?
>
> --
> Best regards,
>  Alex                          mailto:[EMAIL PROTECTED]
>
>
> >
>


-- 
"Bureaucrat Conrad, you are technically correct -- the best kind of correct."

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django developers" 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/django-developers?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to