Ashley wrote:
On Apr 11, 2008, at 1:10 PM, Stephen Sykes wrote:
Ashley wrote:
On Apr 11, 2008, at 11:55 AM, Stephen Sykes wrote:
Chisel - What is so odd in passing the tag id to the controller for the "by_tag" feature?


I think this is the issue: "Other users also tagged this 27." The tag is the human readable part of the record. :)

I'm still not getting this. :-\

Once a new tag is added to the database the tag id will never change, only the tag weight. Tag id is unique and is primary. I suppose the tag description could be used with an index on that column for performance. That would make sense, if that is your concern.

It's that http://mysite.com/tag/1232 is meaningless to the user. Not that it's programatically incorrect; which, as you know, it's not. http://mysite.com/tag/pangolins is better UI.

Well, I'm going to channel for the black part of my heart that mst is responsible for.... :-)

This is much like the quandry:

/users/146     for admin purposes vs.
/users/claco   for humans on a browse

choosing one or the other always seems to lead to problems.. so taking a tip from RHOX, do both...

/tag/name/<name>
/tag/id/<id>

The greatness of future possibilities is expanded to much happiness. Chained/sub instance() make all the code behind either option JustWork.

-=Chris

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
List: [email protected]
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/[email protected]/
Dev site: http://dev.catalyst.perl.org/

Reply via email to