What I've done is to have separate sub-index pages for each section and
specify the appropriate screen and action directory in each sub-index page.
I'm also integrating PHPlib into a FreeEnergy/FreeTrade framework so this
structure allows me to include varying levels of security, database access,
and session tracking depending on what the user is doing.
FreeEnergy is the most sensible development framework I've come across. If I
can just get a template parser working for the screens so my designers don't
have to see any code it will be perfect.
Earl Wyllie
> From: "Leon Atkinson" <[EMAIL PROTECTED]>
> Reply-To: "FreeTrade" <[EMAIL PROTECTED]>
> Date: Fri, 12 May 2000 13:11:43 -0400
> To: "FreeTrade" <[EMAIL PROTECTED]>
> Subject: RE: [FreeTrade] Actions in one directory
>
>> This might not be the best place to ask this question, but
>> I�m sure that Leon or JJ have an answer for it.
>> How come there are no subdirectories below action and screens?
>> Like, why not have a directory action/admin? Is there
>> something insecure about it?
>> How do search engines index pages with a �/� in them?
>
> This is a good question.
>
> When building a site with FreeEnergy (the basic framework of screens,
> actions, etc), we have often put subdirectories in the screens
> directory. Instead of passing them like "SCREEN=about/about_us", though,
> we add an element to the ScreenInfo array that tells the system which
> section the screen is in. That means you still have to have unique
> screen names, but the URL can have "SCREEN=about_us". I didn't make
> subdirectories in FreeTrade because there really aren't that many screens.
> But if you add a bunch of content to a FreeTrade site, you probably should
> use subdirectories.
>
> As far as actions go, there's no ActionInfo array, so you would have to
> pass things as "ACTION=admin/ADD_ITEM". This will work. There's something
> about it that doesn't seem right to me, but I can't offer any reason not
> to do it. I feel there aren't enough actions to justify doing it.
>
> There is a check being made in index.php3 for actions that contain anything
> other than letters, numbers and underscores. That's to prevent actions
> like "ACTION=../../../../../etc/passwd". If you start allowing slashes in
> your actions, you'll have to be more sophisticated with your filtering of
> bad action values.
>
> As far as putting slashes in an URL, I don't think there are issues with
> browsers having slashes in the query string. It might confuse some
> spiders, but spiders rarely follow links with query strings anyway.
>
> Leon
>
> ------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Site: http://www.working-dogs.com/freetrade/
> Problems?: [EMAIL PROTECTED]
>
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Site: http://www.working-dogs.com/freetrade/
Problems?: [EMAIL PROTECTED]
