To be honest... I like this idea. Who says the normale rule of thumb is you shouldn't put recognizable info in a url or post ? Why is it then that blogging and cms tools lately are getting more and more modules and extensions for not only 'search engine friendly' but also 'userfriendly' url's ? Your domain name probably makes sense - why shouldn't the rest of your url ?
Maybe you could even do it like this: If url is like 'event/yyyy':show all events of that year. If url is like 'event/yyyy/mm':show all events of that year/month If url is like 'event/august' or 'event/08':show all events this year in august... And so on... Maybe I didn't sleep enough last night and I'm babbling, but I always felt the url is part of your user interface. I have done a rewrite of a sort of calender/directory system a while ago to have more searchengine (and user) friendly url's, and although the content stayed the same, much more pages were indexed and traffic coming from searchengines really boomed. Piet. > -----Original Message----- > From: James Keeline [mailto:[EMAIL PROTECTED] > Sent: woensdag 3 augustus 2005 19:23 > To: [email protected] > Subject: Re: [php-list] incrementation, the not-so-normal way > > > > So, I had a crazy (and probably dumb) idea. :) > > > > I'm setting up a calendar of events, with a full db > back-end. The end > > result is to have the events pulled like event.php?id=1000 Straight > > forward. > > > > but then, i go thinking.. "Wouldn't it be more productive, and > > meaningful, if the id actually meant something?" > > > > Here's what i'm thinking-- event.php?id=yyyymmddhhmm_(and > some 1,2,3 > > or > > a,b,c character here if there is more than one at that > given day/time) > > > > with this syntax, I can easily mod-rewrite it into a nice and clean > > event/yyyy/mm/dd/hh/mm/index.php > > > > > > What's your thoughts on using this style, vs an > auto-increment id field? > > Would you anticipate any problems? > > > Although you can do this, the act of adding a letter makes > your primary key field less efficient than an integer field. > Indexing the field could help. > > The normal rule of thumb is that you shouldn't put > information that is easily recognizable in the URL or POST. > Ultimately, it depends on the nature of your application. If > it is a free calendar and you don't care who sees which > events, then perhaps you can do this effectively. > > James > _____ > > James D. Keeline > http://www.Keeline.com http://www.Keeline.com/articles > http://Stratemeyer.org > http://www.Keeline.com/TSCollection > > > http://www.ITeachPHP.com -- Free Computer Classes: Linux, PHP, etc. Summer Semester Begins Jun 20 -- New Classes Start Every Few Weeks. Community email addresses: Post message: [email protected] Subscribe: [EMAIL PROTECTED] Unsubscribe: [EMAIL PROTECTED] List owner: [EMAIL PROTECTED] Shortcut URL to this page: http://groups.yahoo.com/group/php-list Yahoo! Groups Links ------------------------ Yahoo! Groups Sponsor --------------------~--> <font face=arial size=-1><a href="http://us.ard.yahoo.com/SIG=12h73vll2/M=362335.6886445.7839731.1510227/D=groups/S=1705005703:TM/Y=YAHOO/EXP=1123166954/A=2894361/R=0/SIG=13jmebhbo/*http://www.networkforgood.org/topics/education/digitaldivide/?source=YAHOO&cmpgn=GRP&RTP=http://groups.yahoo.com/";>In low income neighborhoods, 84% do not own computers. At Network for Good, help bridge the Digital Divide!</a>.</font> --------------------------------------------------------------------~-> Community email addresses: Post message: [email protected] Subscribe: [EMAIL PROTECTED] Unsubscribe: [EMAIL PROTECTED] List owner: [EMAIL PROTECTED] Shortcut URL to this page: http://groups.yahoo.com/group/php-list Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/php-list/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
