IS it best to configure permissions within a website for Administration access, separate webPages, or a completely separate application to administer changes on the site?
I usually configure permissions within the same website and have separate web pages for administration.
In some cases, having the same page with more controls can be useful as well, for instance, if you want a page to Approve/Reject comments, or something like that, instead of creating a separate interface you just add a few buttons depending on the role of the logged in user.
I often find that with questions starting "Is it best to" that there s usually a someone and a sometime involved (a kind of pragmatics type thinking - whome and in what context)
不同的环境将针对您在此处提出的每个方案提供不同的优缺点,并且根据需要哪些功能的人可能也会影响您的选择。
With regard to the "who" part there may be other questions you ll be asking yourself about the process you re going through. Is it my users that require admin access, is it my development team, is it the managing director with little I.T. experience etc etc.
关于使用的媒介可能会对您的决策起到一定作用。 "管理员"人员会使用PC,销售代表会使用掌上电脑在路上使用适合自己的软件应用程序等。
- winforms
- combobox
- fogbugz
- java
- date
- internationalization
- asp.net
- iis
- url-rewriting
- urlrewriter
- c#
- enums
- ocaml
- haxe
- algorithm
- string
- viewstate
- .net
- c++
- c
- symbol-table
- mysql
- database
- postgresql
- licensing
- migration
- vb.net
- vb6
- declaration
- vb6-migration
- python
- psycopg2
- backup
- vmware
- virtualization
- gnu-screen
- authentication
- desktop
- excel
- xll
- cultureinfo
- regioninfo
- oracle
- client
- session
- download
- html
- virtual
- constructor
- scenarios
- perl
- full-text-search
- javascript
- ajax
- testing
- oop
- inheritance
- vim
- encapsulation
- information-hiding