App organization
App organization
- Subject: App organization
- From: email@hidden
- Date: Sun, 23 Jul 2006 12:17:08 -0700
In my day job I build websites the old fashioned way, using scripting
languages, and I would organize the site I'm building something like
this:
User pages are generally at the root of the site, so we might have
/ - home page
/panels - list of all panels of license plates (these are pictures of
the panels in the museum)
/panel-detail - info about a selected panel
Admin pages are in their own directory (which shows up in the URL)
/admin - list of available tasks
/admin/add - add a new panel
And so on.
I know that it is standard practice to use Apache Rewrite Rules to
make pretty URLs, and I presume I could probably get my site to work
this way if I wanted to, but I have a hunch that this is not the WO Way.
I have read that some folks make the admin pages a separate
application, but in this case that seems like overkill; the main
site will contain 3 or 4 pages. On the other hand I would like to
use Apache to password protect the admin area, so I don't have to
implement user logins in my first app, and that means I do need
something in the URL to hang that off of.
So... what would be the proper WO Way to approach this?
thanks,
janine
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden