[问]关于本网站设计的意见 [英] [Q] Opinions on this site design
问题描述
这只是我头脑中的一个想法，我想就如何设计我的网站获得一些
的意见。
首先，它将是一个100％（或非常接近它）的PHP网站。
描述这个想法的最好方法是给出具体的
例子。
该网站将围绕一个.php文件... index.php。
这是两个专栏网站。左栏是常见的导航栏
，右栏是（显然）内容栏。
该站点还涉及用户注册和登录访问权限。
因此，如果用户未登录，则左栏将包含常用的
用户名和密码字段。下面是两个链接''注册''
和'忘记密码''。
假设新用户需要注册。然后他们将点击注册链接进入
。
我发现大多数网站都会将用户带到，对于
例如，http：//< address> /register.php
这是我正在考虑的替代方案的主要内容。
''注册''链接将是：
http：//< address> /index.php？func = register
现在，我的php代码会看到'func''被分配，并会调用
a函数，将相应的内容放在正确的列中。 />
在注册案例中，它将是
用户的标准请求项目（电子邮件，所需用户名，所需密码）。
以同样的方式，''忘记密码''链接将是：
http：//< address> /index.php？func =忘记密码
现在，func基本上代表了我网站的顶级部分/>
顶级部分将包含子部分。我会通过
来处理这个问题，主要做以下事情：
http：//< address> /index.php？func =< majorsection>& ; param1 = someinformati on
为了防止index.php从远到大增长，主要部分将在他们自己的.php文件中处理。 index.php基本上只是一个
大if / elseif语句基于func所说的（或者没说）。
如果是用户，谁没有登录，试图通过
提供func来访问网站的一部分，访问将被拒绝通过公共会话
管理提供的PHP。
人们怎么想？
-
== Eric Gorr ===== ==== http://www.ericgorr.net ======= == ICQ：9293199 ===
因此，智能的考虑总是包括
的利益和伤害。 - 孙子
==侮辱，就像暴力一样，是无能的最后避难所...... ===
< BLOCKQUOTE>"埃里克" <例如************* @ verizon.net>在消息中写道
新闻：1g3sw11.le82pbmhdazrN％例如************* @ verizon .net ...
这只是一个我此刻想到了我的想法，我想就如何设计我的网站提出一些意见。
首先，它将是100％（或非常接近它）PHP网站。
描述这个想法的最好方法是给出一个特定的
示例。
该网站将围绕一个.php文件... index.php。
这是一个两列网站。左栏是一个常用的导航栏
，右栏是（显然）内容栏。
该站点还涉及用户注册和登录访问。
因此，如果用户未登录，则左栏将包含常用的用户名和密码字段。在这些下面是两个链接''注册''
和'忘记密码''。
假设新用户需要注册。然后他们将继续点击注册链接。
我发现大多数网站都会将用户带到用户手中，例如， http：//< address> /register.php
以下是我正在考虑的替代方案。
注册链接将是：
http：//< address> /index.php？func = register
现在，我的php代码会看到''func''被分配并将调用
一个将适当的内容放在右栏中的功能。
在注册的情况下，它将是
用户的标准请求项目（电子邮件，期望）用户名，所需的密码）。
以同样的方式，''忘记密码''链接将是：
http：//< address> /index.php ？func = forgotpassword
现在，func基本上代表了我网站的顶级部分。
顶级部分将包含子部分。我会通过以下方式处理这个问题：
http：//< address> /index.php？func =< majorsection>& param1 = someinformati on
为了防止index.php从远到大的增长，主要部分将在他们自己的.php文件中处理。 index.php基本上只是一个基于func所说（或没说）的if / elseif语句。
如果用户没有登录，则尝试通过提供func来访问网站的一部分，通过PHP提供的公共会话管理将拒绝访问。
人们怎么想？ / blockquote>
人们认为这是每天都做的。
SwissCheese< Sw *** ******@cfl.rr.com>写道：
人们认为这是每天都做的。
有趣。
我还没有找到一个完全基于这个想法的网站。
你能指向一个吗？
现在，考虑到有很少有单一的解决方案可以解决所有问题，设计会以什么方式破坏？
-
== Eric Gorr == ======= http://www.ericgorr.net ==== ===== ICQ：9293199 ===
因此，智能的考虑总是包括
的利益和伤害。 - 孙子
==侮辱，就像暴力一样，是无能的最后避难所... ===
雕刻在神秘的符文中在非常活泼的岩石上，埃里克的最后一句话
的comp.lang.php表明：
SwissCheese< Sw ****** ***@cfl.rr.com>写道：
人们认为这是每天都做的。
有趣。
我还没有找到一个完全基于这个想法的网站。
你能指出一个吗？
我不知道我会说'每天都在做。我没有任何
统计数据或任何东西，但在我看来，在不同文件中有不同的
函数更常见。也就是说，Phormation按照你b $ b描述的方式完成，所有链接都指向索引文件，根据指示的功能输入
代码。
-
Alan Little
Phorm PHP表单处理器
http://www.phorm.com/
This is just a thought in my head at the moment and I wanted to get some
opinions on an idea on how to design my web site.
First, it would be a 100% (or very close to it) PHP site.
The best way to descibe this thought would be to give a specific
example.
The site would revolve around a single .php file...index.php.
It is a two column site. The left column is a common navigation column
and the right column is (obviously) the content column.
The site also involve user registration and login for access.
So, if a user is not logged, the left column would contain the common
username and password fields. Just below these are two links ''Register''
and ''Forgot Password''.
Assume that a new user needs to register. They would then proceed to
click on the ''Register'' link.
What I have found that most sites do would be to take the user to, for
example, http://<address>/register.php
Here is the meat of the alternative I was considering.
The ''Register'' link would be:
http://<address>/index.php?func=register
Now, my php code would then see that ''func'' was assigned and would call
a function that would put the appropriate content in the right column.
In the ''Register'' case, it would be the standard request items ask of
users (e-mail, desired username, desired password).
In the same manner, the ''Forgot Password'' link would be:
http://<address>/index.php?func=forgotpassword
Now, func would essentially represent top level sections of my site.
The top level sections will have sub-sections. I would handle this by
essentially doing the following:
http://<address>/index.php?func=<majorsection>¶m1=someinformati on
To keep index.php from growing just far to big, the major sections would
be handled in their own .php files. index.php would basically be just a
large if/elseif statement based on what func said (or did not say).
If a user, who wasn''t logged in, attempted to access part of the site by
providing a ''func'', access would be denied via the common session
management provided by PHP.
What do people think?
--
== Eric Gorr ========= http://www.ericgorr.net ========= ICQ:9293199 ===
"Therefore the considerations of the intelligent always include both
benefit and harm." - Sun Tzu
== Insults, like violence, are the last refuge of the incompetent... ===
"Eric" <eg*************@verizon.net> wrote in message
news:1g3sw11.le82pbmhdazrN%eg*************@verizon .net...This is just a thought in my head at the moment and I wanted to get some
opinions on an idea on how to design my web site.
First, it would be a 100% (or very close to it) PHP site.
The best way to descibe this thought would be to give a specific
example.
The site would revolve around a single .php file...index.php.
It is a two column site. The left column is a common navigation column
and the right column is (obviously) the content column.
The site also involve user registration and login for access.
So, if a user is not logged, the left column would contain the common
username and password fields. Just below these are two links ''Register''
and ''Forgot Password''.
Assume that a new user needs to register. They would then proceed to
click on the ''Register'' link.
What I have found that most sites do would be to take the user to, for
example, http://<address>/register.php
Here is the meat of the alternative I was considering.
The ''Register'' link would be:
http://<address>/index.php?func=register
Now, my php code would then see that ''func'' was assigned and would call
a function that would put the appropriate content in the right column.
In the ''Register'' case, it would be the standard request items ask of
users (e-mail, desired username, desired password).
In the same manner, the ''Forgot Password'' link would be:
http://<address>/index.php?func=forgotpassword
Now, func would essentially represent top level sections of my site.
The top level sections will have sub-sections. I would handle this by
essentially doing the following:
http://<address>/index.php?func=<majorsection>¶m1=someinformati on
To keep index.php from growing just far to big, the major sections would
be handled in their own .php files. index.php would basically be just a
large if/elseif statement based on what func said (or did not say).
If a user, who wasn''t logged in, attempted to access part of the site by
providing a ''func'', access would be denied via the common session
management provided by PHP.
What do people think?
People think that this is done every day.
SwissCheese <Sw*********@cfl.rr.com> wrote:
People think that this is done every day.
Interesting.
I have yet to find a site that is based solely around this idea.
Can you point to one?
Now, considering that there is rarely a single solution that solves all
problems, in what ways would the design break down?
--
== Eric Gorr ========= http://www.ericgorr.net ========= ICQ:9293199 ===
"Therefore the considerations of the intelligent always include both
benefit and harm." - Sun Tzu
== Insults, like violence, are the last refuge of the incompetent... ===
Carved in mystic runes upon the very living rock, the last words of Eric
of comp.lang.php make plain:
SwissCheese <Sw*********@cfl.rr.com> wrote:People think that this is done every day.
Interesting.
I have yet to find a site that is based solely around this idea.
Can you point to one?
I don''t know that I''d say it''s done every day. I don''t have any
statistics or anything, but it seems to me more common to have different
functions in different files. That said, Phormation is done the way you
describe, with all links pointing back to the index file, which pulls in
code according to the functionality indicated.
--
Alan Little
Phorm PHP Form Processor
http://www.phorm.com/
这篇关于[问]关于本网站设计的意见的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
