菜单
  

    The Java approach is to prevent these problems from occurring, via the sandbox. The Java interpreter that lives on your local Web browser examines the applet for any untoward instructions as the applet is being loaded. In particular, the applet cannot write files to disk or erase files (one of the mainstays of viruses). Applets are generally considered to be safe, and since this is essential for reliable client/server systems, any bugs in the Java language that allow viruses are rapidly repaired. (It’s worth noting that the browser software actually enforces these security restrictions, and some browsers allow you to select different security levels to provide varying degrees of access to your system.) You might be skeptical of this rather draconian restriction against writing files to your local disk. For example, you may want to build a local database or save data for later use offline. The initial vision seemed to be that eventually everyone would get online to do anything important, but that was soon seen to be impractical (although low-cost “Internet appliances” might someday satisfy the needs of a significant segment of users). The solution is the “signed applet” that uses public-key encryption to verify that an applet does indeed come from where it claims it does. A signed applet can still trash your disk, but the theory is that since you can now hold the applet creator accountable they won’t do vicious things. Java provides a framework for digital signatures so that you will eventually be able to allow an applet to step outside the sandbox if necessary. Digital signatures have missed an important issue, which is the speed that people move around on the Internet. If you download a buggy program and it does something untoward, how long will it be before you discover the damage? It could be days or even weeks. By then, how will you track down the program that’s done it? And what good will it do you at that point?
    7.Internet vs. intranet
    The Web is the most general solution to the client/server problem, so it makes sense that you can use the same technology to solve a subset of the problem, in particular the classic client/server problem within a company. With traditional client/server approaches you have the problem of multiple types of client computers, as well as the difficulty of installing new client software, both of which are handily solved with Web browsers and client-side programming. When Web technology is used for an information network that is restricted to a particular company, it is referred to as an intranet. Intranets provide much greater security than the Internet, since you can physically control access to the servers within your company. In terms of training, it seems that once people understand the general concept of a browser it’s much easier for them to deal with differences in the way pages and applets look, so the learning curve for new kinds of systems seems to be reduced.
    The security problem brings us to one of the pisions that seems to be automatically forming in the world of client-side programming. If your program is running on the Internet, you don’t know what platform it will be working under, and you want to be extra careful that you don’t disseminate buggy code. You need something cross-platform and secure, like a scripting language or Java. 
    If you’re running on an intranet, you might have a different set of constraints. It’s not uncommon that your machines could all be Intel/Windows platforms. On an intranet, you’re responsible for the quality of your own code and can repair bugs when they’re discovered. In addition, you might already have a body of legacy code that you’ve been using in a more traditional client/server approach, whereby you must physically install client programs every time you do an upgrade. The time wasted in installing upgrades is the most compelling reason to move to browsers, because upgrades are invisible and automatic. If you are involved in such an intranet, the most sensible approach to take is the shortest path that allows you to use your existing code base, rather than trying to recode your programs in a new language.
  1. 上一篇:情感分析观点挖掘英文文献和中文翻译
  2. 下一篇:ASP.NET技术英文文献及中文翻译
  1. 会计师事务所任期与审计...

  2. ZigBee-RFID混合网络的节电英文文献和中文翻译

  3. ADO.NET结构与概述英文文献和中文翻译

  4. 信息系统开发与数据库开...

  5. 机器人学入门力学与控制英文文献和中文翻译

  6. 园林植物景观的园林绿化...

  7. 人工神经网络的电液比例...

  8. 中国传统元素在游戏角色...

  9. C++最短路径算法研究和程序设计

  10. 巴金《激流三部曲》高觉新的悲剧命运

  11. 浅析中国古代宗法制度

  12. NFC协议物理层的软件实现+文献综述

  13. 上市公司股权结构对经营绩效的影响研究

  14. 江苏省某高中学生体质现状的调查研究

  15. 高警觉工作人群的元情绪...

  16. g-C3N4光催化剂的制备和光催化性能研究

  17. 现代简约美式风格在室内家装中的运用

  

About

优尔论文网手机版...

主页:http://www.youerw.com

关闭返回