What are the differences in considerations in respect to designing or developing an Intranet and an Internet application ?
在设计或开发Intranet和Internet应用程序方面有哪些不同之处?
10 个解决方案
#1
4
One other thing, in an intranet environment you will generally have a standard client build meaning that you can code to a specific browser & version (ha, IE6 normally).
另一件事,在Intranet环境中,您通常会有一个标准的客户端构建,这意味着您可以编写特定的浏览器和版本(通常是ha,IE6)。
Out in the wilds of the internet, you have to deal with all sorts of browsers & versions, so your html/css/js needs to handle all of these.
在互联网的荒野中,你必须处理各种浏览器和版本,所以你的html / css / js需要处理所有这些。
#2
4
On an intranet, you may be able to take advantage of existing authentication and authorization services. The banks I've worked for have had very secure third-party authentication services. At other companies using Windows platforms, Active Directory can be useful for both authentication and authorization (using "groups" to define roles).
在Intranet上,您可以利用现有的身份验证和授权服务。我工作的银行拥有非常安全的第三方认证服务。在使用Windows平台的其他公司,Active Directory可用于身份验证和授权(使用“组”来定义角色)。
When these features are available, you don't have to make as many decisions about hashing (and salting) or encrypting passwords, password strength, password expiration, and such. And you don't have to create all the admin pages for setting up users, retrieving or resetting passwords, etc. Users are not confronted with different password policies on different intranet applications, and can often use the same login credentials for multiple applications.
当这些功能可用时,您无需做出关于散列(和腌制)或加密密码,密码强度,密码到期等的许多决定。并且您不必创建用于设置用户,检索或重置密码等的所有管理页面。用户在不同的Intranet应用程序上不会遇到不同的密码策略,并且通常可以为多个应用程序使用相同的登录凭据。
Not having to deal with all of this leaves you more time to spend on the application's main features.
不必处理所有这些使您有更多时间花在应用程序的主要功能上。
Even though an intranet environment may seem to be less threatened by hackers, it only takes one breach to compromise the system. And, an intranet may be dealing with extremely sensitive data. So, I think you need to make intranet applications at least as secure as Internet applications.
即使内部网环境似乎受到黑客的威胁较小,但只需要一次破坏就可以破坏系统。并且,内联网可能正在处理极其敏感的数据。因此,我认为您需要使Intranet应用程序至少与Internet应用程序一样安全。
#3
3
Intranet applications can take advantage of the ability to link to resources on internal UNC paths (e.g. \\corporateserver\devteam\ArchitectureDiagram.vsd).
Intranet应用程序可以利用链接到内部UNC路径上的资源的能力(例如\\ corporateserver \ devteam \ ArchitectureDiagram.vsd)。
However, be aware that browsers differ in how they handle such links. In Firefox, by default, clicking a link to a resource on a UNC path silently fails (clicking the link does nothing); some workarounds for this are available. In Internet Explorer, links to UNC path resources do work by default.
但请注意,浏览器处理此类链接的方式不同。在Firefox中,默认情况下,单击指向UNC路径上资源的链接会无效(单击该链接不会执行任何操作);可以使用一些解决方法。在Internet Explorer中,默认情况下,指向UNC路径资源的链接可以正常工作。
#4
2
Some considerations...
- Security
- Site IO
- Traffic
- Data Model
- Need for scalability
需要可扩展性
#5
1
Galwegian have wrote most of them already but I think you should consider more caching when it goes external because your database might be more active.
Galwegian已经写了大部分内容,但我认为你应该考虑更多缓存,因为你的数据库可能更活跃。
An other point is when you are inside your business (intranet) you might be able to use lower security parameter to access hard drive of you user. This is not possible with external website/application via the web.
另一点是,当您进入业务(Intranet)时,您可能可以使用较低的安全性参数来访问您的用户的硬盘驱动器。外部网站/应用程序无法通过网络进行此操作。
#6
0
Intranets often have a fixed set of browsers that are supported.
内联网通常具有一组受支持的固定浏览器。
If you're lucky you can get away with ignoring IE6. Which is nice.
如果你很幸运,你可以忽略IE6。这很好。
#7
0
It might be more productive to think of the similarities in design considerations.
考虑设计考虑因素的相似性可能会更有成效。
You still need to ask yourself the same basic questions about what you are trying to solve, for who, what are their capabilities, what platform(s) do you have access to...etc.
你仍然需要问自己同样的基本问题,关于你想要解决的问题,你的能力,能力是什么,你有什么平台可以访问...等等。
The differences will become apparent quickly enough if you give appropriate consideration to the scope. Many of these have been signposted by other contributors here, but try and avoid making too many assumptions up-front.
如果您适当考虑范围,差异将很快变得明显。其中许多已被其他贡献者标示,但请尽量避免在前面做出太多假设。
#8
0
Please don't make the mistake of thinking that, because an app is exclusive to the intranet, that it doesn't need to be as secure as an internet app. If anything, it needs to be more secure, as there's a good chance it will be processing data more sensitive than the data the company's internet applications process.
请不要错误地认为,因为应用程序是Intranet独有的,它不需要像Internet应用程序那样安全。如果有的话,它需要更安全,因为处理数据的可能性比公司的互联网应用程序处理的数据更敏感。
If you rely on the security of the intranet, then your app will only be as secure as the intranet (and as secure as the weakest of all its users, who have their passwords written on sticky notes on their monitors).
如果您依赖于Intranet的安全性,那么您的应用程序将只能像Intranet一样安全(并且与所有用户中最弱的用户一样安全,他们的密码写在监视器上的便签上)。
#9
0
@Galwegian and others:
@Galwegian和其他人:
- Time to application live. In public internet many amateur and marketing-corporate campaign has quite short use time (1-2 years?). As such, accept "chaotic" design and chaotic ad-hoc technologies. Then amateur has no energy to develop, new marketing director has new BIG budget for NEW colourful software etc ;)
申请时间。在公共互联网上,许多业余和营销企业活动的使用时间相当短(1 - 2年?)。因此,接受“混乱”设计和混乱的ad-hoc技术。然后业余人士没有精力去开发,新营销总监为新的丰富多彩的软件等提供了新的大预算;)
Important "hard" business software must live, (be extended, developed) for example 8-10 years and more, without pause.
重要的“硬”商业软件必须存在,(扩展,开发),例如8 - 10年甚至更长时间,没有停顿。
#10
-1
Intranet Application are more for internal staffig and knowledge managemnet purposes..
Intranet应用程序更适用于内部人员和知识管理目的..
its more moe sensative data to be shared within a network
它在网络*享更多的敏感数据
http://www.dreamznetsolutions.com/intranet_application_development_mumbai.html
#1
4
One other thing, in an intranet environment you will generally have a standard client build meaning that you can code to a specific browser & version (ha, IE6 normally).
另一件事,在Intranet环境中,您通常会有一个标准的客户端构建,这意味着您可以编写特定的浏览器和版本(通常是ha,IE6)。
Out in the wilds of the internet, you have to deal with all sorts of browsers & versions, so your html/css/js needs to handle all of these.
在互联网的荒野中,你必须处理各种浏览器和版本,所以你的html / css / js需要处理所有这些。
#2
4
On an intranet, you may be able to take advantage of existing authentication and authorization services. The banks I've worked for have had very secure third-party authentication services. At other companies using Windows platforms, Active Directory can be useful for both authentication and authorization (using "groups" to define roles).
在Intranet上,您可以利用现有的身份验证和授权服务。我工作的银行拥有非常安全的第三方认证服务。在使用Windows平台的其他公司,Active Directory可用于身份验证和授权(使用“组”来定义角色)。
When these features are available, you don't have to make as many decisions about hashing (and salting) or encrypting passwords, password strength, password expiration, and such. And you don't have to create all the admin pages for setting up users, retrieving or resetting passwords, etc. Users are not confronted with different password policies on different intranet applications, and can often use the same login credentials for multiple applications.
当这些功能可用时,您无需做出关于散列(和腌制)或加密密码,密码强度,密码到期等的许多决定。并且您不必创建用于设置用户,检索或重置密码等的所有管理页面。用户在不同的Intranet应用程序上不会遇到不同的密码策略,并且通常可以为多个应用程序使用相同的登录凭据。
Not having to deal with all of this leaves you more time to spend on the application's main features.
不必处理所有这些使您有更多时间花在应用程序的主要功能上。
Even though an intranet environment may seem to be less threatened by hackers, it only takes one breach to compromise the system. And, an intranet may be dealing with extremely sensitive data. So, I think you need to make intranet applications at least as secure as Internet applications.
即使内部网环境似乎受到黑客的威胁较小,但只需要一次破坏就可以破坏系统。并且,内联网可能正在处理极其敏感的数据。因此,我认为您需要使Intranet应用程序至少与Internet应用程序一样安全。
#3
3
Intranet applications can take advantage of the ability to link to resources on internal UNC paths (e.g. \\corporateserver\devteam\ArchitectureDiagram.vsd).
Intranet应用程序可以利用链接到内部UNC路径上的资源的能力(例如\\ corporateserver \ devteam \ ArchitectureDiagram.vsd)。
However, be aware that browsers differ in how they handle such links. In Firefox, by default, clicking a link to a resource on a UNC path silently fails (clicking the link does nothing); some workarounds for this are available. In Internet Explorer, links to UNC path resources do work by default.
但请注意,浏览器处理此类链接的方式不同。在Firefox中,默认情况下,单击指向UNC路径上资源的链接会无效(单击该链接不会执行任何操作);可以使用一些解决方法。在Internet Explorer中,默认情况下,指向UNC路径资源的链接可以正常工作。
#4
2
Some considerations...
- Security
- Site IO
- Traffic
- Data Model
- Need for scalability
需要可扩展性
#5
1
Galwegian have wrote most of them already but I think you should consider more caching when it goes external because your database might be more active.
Galwegian已经写了大部分内容,但我认为你应该考虑更多缓存,因为你的数据库可能更活跃。
An other point is when you are inside your business (intranet) you might be able to use lower security parameter to access hard drive of you user. This is not possible with external website/application via the web.
另一点是,当您进入业务(Intranet)时,您可能可以使用较低的安全性参数来访问您的用户的硬盘驱动器。外部网站/应用程序无法通过网络进行此操作。
#6
0
Intranets often have a fixed set of browsers that are supported.
内联网通常具有一组受支持的固定浏览器。
If you're lucky you can get away with ignoring IE6. Which is nice.
如果你很幸运,你可以忽略IE6。这很好。
#7
0
It might be more productive to think of the similarities in design considerations.
考虑设计考虑因素的相似性可能会更有成效。
You still need to ask yourself the same basic questions about what you are trying to solve, for who, what are their capabilities, what platform(s) do you have access to...etc.
你仍然需要问自己同样的基本问题,关于你想要解决的问题,你的能力,能力是什么,你有什么平台可以访问...等等。
The differences will become apparent quickly enough if you give appropriate consideration to the scope. Many of these have been signposted by other contributors here, but try and avoid making too many assumptions up-front.
如果您适当考虑范围,差异将很快变得明显。其中许多已被其他贡献者标示,但请尽量避免在前面做出太多假设。
#8
0
Please don't make the mistake of thinking that, because an app is exclusive to the intranet, that it doesn't need to be as secure as an internet app. If anything, it needs to be more secure, as there's a good chance it will be processing data more sensitive than the data the company's internet applications process.
请不要错误地认为,因为应用程序是Intranet独有的,它不需要像Internet应用程序那样安全。如果有的话,它需要更安全,因为处理数据的可能性比公司的互联网应用程序处理的数据更敏感。
If you rely on the security of the intranet, then your app will only be as secure as the intranet (and as secure as the weakest of all its users, who have their passwords written on sticky notes on their monitors).
如果您依赖于Intranet的安全性,那么您的应用程序将只能像Intranet一样安全(并且与所有用户中最弱的用户一样安全,他们的密码写在监视器上的便签上)。
#9
0
@Galwegian and others:
@Galwegian和其他人:
- Time to application live. In public internet many amateur and marketing-corporate campaign has quite short use time (1-2 years?). As such, accept "chaotic" design and chaotic ad-hoc technologies. Then amateur has no energy to develop, new marketing director has new BIG budget for NEW colourful software etc ;)
申请时间。在公共互联网上,许多业余和营销企业活动的使用时间相当短(1 - 2年?)。因此,接受“混乱”设计和混乱的ad-hoc技术。然后业余人士没有精力去开发,新营销总监为新的丰富多彩的软件等提供了新的大预算;)
Important "hard" business software must live, (be extended, developed) for example 8-10 years and more, without pause.
重要的“硬”商业软件必须存在,(扩展,开发),例如8 - 10年甚至更长时间,没有停顿。
#10
-1
Intranet Application are more for internal staffig and knowledge managemnet purposes..
Intranet应用程序更适用于内部人员和知识管理目的..
its more moe sensative data to be shared within a network
它在网络*享更多的敏感数据
http://www.dreamznetsolutions.com/intranet_application_development_mumbai.html