[Catalyst] website member urls

[Charles]

John,

John,
technically, you're correct in that I should consider placing the usernames=
 under /user. But I'm thinking of the fuzzy (to me) usability issues involv=
ed and the   http://website.com/meme is what hundreds of millions non-devel=
oper users have come to expect.  Also, fwiw,  http://website.com/is the use=
r's profile which is publically viewable while http://website.com/member/ i=
s the users url when they are logged in.

Thanks so much for your input.

Catalyst Rocks.

-Charles


Are you sure you want to layout your URLs that way, though? You'll *never* =
need other top level items that might conflict with user names? If you put =
all the users under /user (or something like that) then they're in their ow=
n namespace and you won't have problems with name conflicts.
- john romkey
http://www.romkey.com/



________________________________
From: John Romkey <romkey at apocalypse.org>
To: The elegant MVC web framework <catalyst at lists.scsys.co.uk>
Sent: Wednesday, April 29, 2009 5:21:53 PM
Subject: Re: [Catalyst] website member urls


On Apr 29, 2009, at 4:52 PM, Charles wrote:
On Wed, Apr 29, 2009 at 05:31:43PM -0300, Fernan Aguero wrote:
> On Wed, Apr 29, 2009 at 5:23 PM, Charles <cshtreck at yahoo.com> wrote:
> > I'd like someone w/ better catalyst-fu to recommend how I could impleme=
nt
> > urls for members a la myspace and youtube ( ie
> >  http://websiteurl.com/  ) .
> > There's got to be a better way that creating a seperate controller for =
each
> > user.
> =

> sub member : Regex('\S+') {
>  my ($self, $c) =3D @_;

Using Regex for that seems weird to me.

  sub member : Chained(/) Args(1) {
    my ($self, $c, $id) =3D @_;
    ...
  }
hans,

This seems to work, although, i'd have to add logic to have this member con=
troller  ignore the following types of urls

http://websiteurl.com/signup
http://websiteurl.com/members/ <=3D users see this as their url when logged=
 in.
Not at all. You just add handlers for those URLs to your controller; they'r=
e more specific than the member handler and should match.

sub signup : Chained('/') PathPart('signup') Args(0) {
...
}

Are you sure you want to layout your URLs that way, though? You'll *never* =
need other top level items that might conflict with user names? If you put =
all the users under /user (or something like that) then they're in their ow=
n namespace and you won't have problems with name conflicts.
- john romkey
http://www.romkey.com/


      =

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.scsys.co.uk/pipermail/catalyst/attachments/20090429/cd402=
d62/attachment.htm