DOCSLIB.ORG

From the PC to the Network Computer

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
From the PC to the Network Computer CQ ° @»2@w¢cw.,%,¤1 CERN LIBRARIES, GENEVA WIIIIIIIIII|||IIIIIIKIIHIIIIIIIIIHIIIIIIIIIII . I` v~ 2/ W M CERN·CN·96·m6 cERN/cN/96/16 From the PC to the Network Computer. George Shering, CN Division, CERN. Norsk Data minicomputers with CAMAC and Abstract custom Multiplex I/O were replaced by VME The Network Computer is being touted as computers. Although each of these steps the altemative/replacement/successor to the sounded good on its own, taken together the simplicity of the SPS system was lost and the PC. Claimed advantages are lower cost and reduced maintenance effort. Technical l980s’ control systems were no better, and were innovations are a network transferable more manpower consuming, than the 1970s’ interpretive programming language (Java), ones, despite enormously increased computer power and memory. network loadable objects and a simpler stylized user interface. Some of these have been seen before in the "home-built" control Fortunately in the 1990s the PC came along and systems of the 1970s. This paper describes gave a solution to many of the problems. the advantages of our current PC control Unfortunately the "professional computer" systems, traces their development from the tendency which did not like the custom solutions 1970s home-built control systems, and ofthe SPS also resisted the PC control system, speculates on the possible role of the and as recently as the 1991 International Network Computer in Accelerator Control Conference in Tsukuba, proponents of PC Systems. control systems were ridiculed for suggesting that a big accelerator could be controlled by Introduction PCs, some of which were limited to 640K memory (forgetting that the Norsk Data In the l970’s the computer control of machines were sub-64K). I hope this first accelerators was a very hot topic. Accelerators International Conference on PC control systems had progressed beyond the capability of manual signifies a change in attitude. and hardwired control systems, the computer was there and full of promise, but experience The PC control systems of today have not yet and software for accelerator control had not yet solved all the problems, however, but things are become available. The SPS control system was a developing fast and the Network Computer is high water mark of this period. It brought about to appear on stage. The Network together concepts such as the touch panel from Computer, or perhaps more significantly SLAC, interpretive language ideas from Network Computing and the Control Intranet, Rutherford, powerful (for the time) will solve our remaining problems and take us minicomputers from Norsk Data, and welded back to the streamlined solutions of the 1970s them together into a network based control but with full “comrnercial" components. system which became an example for many other control systems, notably at DESY and Claims of the Network Computer KEK. A main claim for the Network Computer is low cost, namely a Network Computer for under The problem with the SPS control system was $500. Cost breakdowns given by Oracle indicate that everything was home designed and custom that this is perfectly possible. The key feature is built. The next generation of developers did not no hard disk, peripherals or expansion sockets. like this (not unreasonably) and an attempt was Just a screen, keyboard, mouse and speakers, made to replace the custom designed elements with "commercial so1utions". The Norsk Data knitted to the network by a single PC board with consoles programmed in Nodal were replaced by gnlysmqdcstamount of mcgmry I¤ 198% the workstations programmed in C. The network /Ih“S‘¤¤¤·¤S cost 5000 erm f<¤eS1¤g*¤ PC bwd md 9 black Md White m¤¤¤<¤» facilities of Nodal were replaced by Remote __ Procedure Calls and Equipment Databases. The wheres a with the Same S¤¤=¤¤ and quanm of electronics cost about 200 francs. If the Mac Paper presented at the International Workshop on PCs and Particle Accelerator Controls, October 7-9 1996, Desy, Hamburg. OCR Output CERN/CN/96/ 16 had been sold at 500 instead of 5000 francs at figure is easily reached if a support person is the time then maybe the PC of today would have needed for every 20 to 30 users. The NICE been a Macintosh! Oracle hope not to repeat that network at CERN attacks this problem head-on ( mistake and to keep the cost of the Network reference 1), and our NICE (Network Integrated Computer down. The only snag is that some full Computing Environment) needs a maximum of spec PCs are heading down to the $500 level as a tenth of this. It should be noted, however, that well! IBM have just announced their "Network Macintosh users quote the simpler installation of Station" at $700 (not counting screen). IBM is Macintosh software as a big advantage here, aiming squarely at replacing the millions of maybe a factor of two. However at CERN there "dumb terminals" connected to its AS/400 is no "NICE" for Macintosh so the support costs minicomputers, primarily in data entry and are indeed much higher for Macintosh than for customer service environments. The Network PC, as are those for Desktop UNIX. The Station gives these users a graphical interface, a Network Computer cuts the cost as there is no mouse, access to the Internet and corporate software to install at all (ROM version), or it is a intranets, and e-mail. standard image down—loaded from a server as for the claimed advantage of the X-terminal. It Low cost is also an important claim for PC should be noted that IBM’s partner for the control systems, compared to workstations and "Network Station" is none other than NCD, the VME crates. This aspect has been ignored for X—terrninal vendor. too long as computers are traditionally a touchy and highly politicized area. It is disturbing, The key to the above two advantages is of course however, when accelerator labs talk about software, not hardware. A Network Computer shortage of money and manpower yet ignore has only one piece of software on board, a Java factors of two or more in any area. The claim is enabled browser. This can be downloaded from that the control system is only a small part of the the network at power-on or built-in on ROM. accelerator so it doesn’t matter if too much The SPS Control System of the 1970s used the money is spent. Studies at CERN in the early same approach. The console software consisted l990’s showed, however, that total expenditure of a Nodal Interpreter with built in facilities for on computing was a significant fraction of the the man-machine interaction. All other laboratory’s disposable materials budget. Cost functionality, in particular all the accelerator studies on the Isolde control system and the control functionality, came down over the Tau—Charm projected facility showed enormous network in the form of Nodal interpretable code cost savings from the use of PC rather than and objects. In the SPS the computer software Workstation+VME. Then there are the claims image was loaded through the network, and for that PC software can lead to big savings in man the first ISOLDE control system which was power and that concentration on one kind of modeled on the SPS one, all the system software computer can bring big savings. It is nice to was in ROM (EPROM) in the CAMAC based have every computer imaginable on site, no ICC. This was similar to the first personal chance of missing out on the latest gadget! The micro-computers where the system software and cost in terms of manpower support is enormous, BASIC was in ROM. This has the advantage of too great in fact, so what we get is reduced faster response at power on with no need to load functionality, e.g. mail in ASCII, inter the system image through the network, and so operability problems, no real expert or support useful network interaction can begin at once. on any one platform. A third claimed advantage of the Network Another claim for the Network Computer is low Computer is ease of use. This springs from two cost of maintenance. An oft—quoted study found factors: firstly only one interface which is fairly that an office PC can cost $8000 per year to simple and becoming well known. The interface maintain. I have just seen another figure of is simpler because everything is a Web page. $13900. This is used by opponents of the PC to The primary interaction is clicking on a picture counter our "low cost" claim. Most of this is or underlined text. Immediate reactions might support manpower cost, however, and is clearly be that this is not rich enough in functionality. very sensitive to the support environment. This Even the SPS control system had fancy gadgets Paper presented at the Intemational Workshop on PCs and Particle Accelerator Controls, October 7-9 1996, Desy, Hamburg. OCR Output CERN/CN/96/ 16 such as a “c0mputcr controlled k110b". When it Applications Programming. came to controlling the Anti—prot0n In the late 1960s the first attempts to harness the Accumulator, despite the fact that it was a "state potential of computers for accelerator control of the art" machine, Simon van der Meer only foundered on the so—called "Software Barrier" wanted a simple touch panel and display, as he In the 1970s people became very aware of this considered this to give adequate interaction and problem and for the SPS the solution was Nodal, all the rest was clutter. And it worked. The an easy to use interpretive language. This was touch panel gave only the equivalent of 16 successful and a wide range of accelerator hypertext links and did indeed prove adequate.
Load more

Recommended publications
  • NORSK DATA AS SINTRAN Iii Reference Manual
    SINTRAN Il Reference Manual NORSK DATA AS SINTRAN IiI Reference Manual ND-60.128.03 NOTICE The information in this document is subject to change without notice. Norsk Data A.S assumes no responsibility for any errors that may appear in this document. Norsk Data A.S assumes no responsibility for-the use or reliability of its software on equipment that is not furnished or supported by Norsk Data A.S. The information described in this document is protected by copyright. It may not be photocopied, reproduced or translated without the prior consent of Norsk Data A.S. Copyright © 1983 by Norsk Data A.S This manual is in loose leaf form for ease of updating. Old pages may be removed and new pages easily inserted if the manual is revised. The loose leaf form also allows you to place the manual in a ring binder (A) for greater protection and convenience of use. Ring binders with 4 rings corre- sponding to the holes in the manual may be ordered in two widths, 30 mm and 40 mm. Use the order form below. The manual may also be placed in a plastic cover (B). This cover is more suitable for manuals of less than 100 pages than for large manuals. Plastic covers may also be ordered below. M= | ~ . IB== B 'S NORSK DATA AS NORSK DATA AS Bil=i & e lll\ ® A Ring Binder B Plastic Cover Please send your order to the local ND office or {in Norway) to: Documentation Department Norsk Data A.S P.0O. Box 4, Lindeberg gérd Oslo 10 ORDER FORM | would like to order Ring Binders, 30 mm, at nkr 20,- per binder Ring Binders, 40 mm, at nkr 25,- per binder Plastic Covers at nkr 10,- per cover NAME ..
    [Show full text]
  • Interfacing Apache HTTP Server 2.4 with External Applications
    Interfacing Apache HTTP Server 2.4 with External Applications Jeff Trawick Interfacing Apache HTTP Server 2.4 with External Applications Jeff Trawick November 6, 2012 Who am I? Interfacing Apache HTTP Server 2.4 with External Applications Met Unix (in the form of Xenix) in 1985 Jeff Trawick Joined IBM in 1990 to work on network software for mainframes Moved to a different organization in 2000 to work on Apache httpd Later spent about 4 years at Sun/Oracle Got tired of being tired of being an employee of too-huge corporation so formed my own too-small company Currently working part-time, coding on other projects, and taking classes Overview Interfacing Apache HTTP Server 2.4 with External Applications Jeff Trawick Huge problem space, so simplify Perspective: \General purpose" web servers, not minimal application containers which implement HTTP \Applications:" Code that runs dynamically on the server during request processing to process input and generate output Possible web server interactions Interfacing Apache HTTP Server 2.4 with External Applications Jeff Trawick Native code plugin modules (uhh, assuming server is native code) Non-native code + language interpreter inside server (Lua, Perl, etc.) Arbitrary processes on the other side of a standard wire protocol like HTTP (proxy), CGI, FastCGI, etc. (Java and \all of the above") or private protocol Some hybrid such as mod fcgid mod fcgid as example hybrid Interfacing Apache HTTP Server 2.4 with External Applications Jeff Trawick Supports applications which implement a standard wire protocol, no restriction on implementation mechanism Has extensive support for managing the application[+interpreter] processes so that the management of the application processes is well-integrated with the web server Contrast with mod proxy fcgi (pure FastCGI, no process management) or mod php (no processes/threads other than those of web server).
    [Show full text]
  • EVOLUTION of Cowtrot SYSTEMS for Aecelsiato&S
    - 271 - EVOLUTION OF COWTROt SYSTEMS FOR AeCELSiAtO&S M.C. Crovley-Milling CRM, Geneva 1, HISTORICAL The ««liest accelerator* wer« quite •»*'. 1, and their controls few, as can be seen from fig. 1 which ahow* the 11-inch eye lot ron built by Lawrence and Livingstone in 1932. Control wm by switches sai variable resistors and indication by a variety of Meters, wired directly iota the appropriate circuit, Where the control eleaemt had to be at high vol• tage, a loop of string vat often uted Co operate it. I1* Figur* t : the 11-inch Cyclotron at Berkeley As the si«* and power of the accelerator* increased, they had to be surrounded by heavier and heavier »hielding, and the controls and indications had to be taken away from the accelerator lt»el£ and transferred to a separate control roo». At first this was done by ju»t extending the cables, keeping each control and indication separate, but the increa• sing number* of value» to be indicated led to some manual switching of instruments between different circuit* to save panel apace. In the 1980's, even though the cyclic, accelerators had grown up to 200 » in diameter, the expense of taking cables for every control element to the control too» was not exce««ive. However, in the i960'», project* of auch larger siae were being considered, where this would no longer be true. The first of theae was the "2-mile" electron lime at SLAC. This is composed of 240 alraott identical taodule*, each aodule having very many controls and indications of interest to the operators, The enormous number of cables which would be required to take all these to the control room was reduced considerably by rentóte awl t i- plexing; that is switching one particular control or indication from each «©«Joie in turn onto the s«se set of cables.
    [Show full text]
  • Vasili Korol
    Vasili Korol Senior Software Developer Odense, Denmark Age: 35 mob.: +45 20 68 50 23 Married, have son (born 2010) e-mail: [email protected] ​ Personal Statement ⚬ Strong IT skills (16+ years of versatile experience) ⚬ Background in physics research ⚬ Work effectively both as team member and leader ⚬ Enthusiastic and committed ⚬ Spoken languages: Russian (native), English (fluent), Danish (Prøve i Dansk 3 / level B2) ​ ​ ​ ​ Education 2006–2008: Master’s degree (with distinction) in applied physics. ​ 2002–2006: Bachelor’s degree (with distinction) in applied physics. Under- to postgraduate student at St. Petersburg State Polytechnical University, Faculty of Physics and Technology, Dept. of Cosmic Physics. The thesis “Search for possible space-time variations of the fine-structure constant and isotopic shifts” (a supervisor Prof. ​ M.G. Kozlov). ​ 1992-2002: School education in St. Petersburg, Russia and Belfast, UK (in 1993). Professional Career 2015 – Feb 2021: Software developer in the QuantBio research group at the University of ​ ​ ​ ​ Southern Denmark (SDU), Institute of Physics, Chemistry and Pharmacy (HPC section). I am the principal developer of VIKING, a service providing a web interface for configuring ​ ​ ​ and running scientific computational tasks on supercomputers. I designed the software architecture, developed the system core and coordinated the work of several developers. 2014 – 2015: Lead programmer (Perl) at Internet Projects LLC, russian informational portals subscribe.ru and sendsay.ru (St. Petersburg, Russia). ​ ​ ​ Worked with a team of developers on projects targeted at developing an API for news aggregation and content processing services. This involved integration with various online platforms (Facebook, Twitter, Vkontakte, LiveJournal, Google Analytics), web scraping and designing instruments for user publications at the portals and beyond.
    [Show full text]
  • TU-P20 How to Survive the Upgrade Treadmill
    HOW TO SURVIVE THE UPGRADE TREADMILL Kirsten Hinsch, Ursula Lauströer, Rüdiger Schmitz, Winfried Schütte - DESY Hamburg, Germany Abstract Lets look a little closer on the impact of changes in Here at DESY we have nine large particle accelerators each part of our environment. and correspondingly a large and complex control system. It consists of subsystems of many generations of hard and 3 IMPACT OF CHANGES software. Until recently we even had to support Norsk Data mini computers so called NORDs. The number of 3.1 Changes in the accelerator applications is considerably more than a thousand. The This is a true place of peace and tranquility. Of course a control team consists of a dozen people aged typically in new accelerator needs a new control system. A closed one the fifties. This large, diverse and understaffed system in- does not need one anymore. Still a major change in the troduces a considerable amount of (healthy) inertia. On accelerator does not necessary have any imp act on the the other hand we have a fast hard- and software upgrade technologies used. It is just a good and most welcome op- cycle in the general computing scene. There is every few portunity to change things now. years a major operating system upgrade. This conflict produces tension and stimulation. 3.2 Network Network upgrades have moderate impact on the other 1 INTRODUCTION areas (fair degree of orthogonality). The major problem we have now is CISCOs mediocre IPX support. We ex- Everybody who works a few years in our field physical- pect this to get worse.
    [Show full text]
  • The Founding, Fantastic Growth, and Fast Decline of Norsk Data AS Tor Steine
    The Founding, Fantastic Growth, and Fast Decline of Norsk Data AS Tor Steine To cite this version: Tor Steine. The Founding, Fantastic Growth, and Fast Decline of Norsk Data AS. 3rd History of Nordic Computing (HiNC), Oct 2010, Stockholm, Sweden. pp.249-257, 10.1007/978-3-642-23315- 9_28. hal-01564615 HAL Id: hal-01564615 https://hal.inria.fr/hal-01564615 Submitted on 19 Jul 2017 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. Distributed under a Creative Commons Attribution| 4.0 International License The Founding, Fantastic Growth, and Fast Decline of Norsk Data AS Tor Olav Steine Formerly of Norsk Data AS [email protected] Abstract. Norsk Data was a remarkable company that in just twenty years went from a glimmer in the eyes of some computer enthusiasts to become number two in share value at the Oslo Stock Exchange. Within a few years thereafter, it collapsed, for no obvious reason. How was this tremendous success possible and why did the company collapse? Keywords: Collapse, computer, F16, industry, minicomputer, Norsk Data, Nord, simulator, success, Supermini 1 The Beginning 1.1 FFI A combination of circumstances led to the founding of Norsk Data1 in June 1967.
    [Show full text]
  • Using Fastcgi with Apache HTTP Server 2.4
    Using FastCGI with Apache HTTP Server 2.4 Jeff Trawick The world of FastCGI Using FastCGI with Apache HTTP Server 2.4 FastCGI with Apache httpd 2.4 Jeff Trawick Choosing mod fcgid http://emptyhammock.com/ mod proxy fcgi [email protected] mod authnz fcgi Other tools April 8, 2014 PHP Applications and FastCGI Future 1/97 Revisions Using FastCGI with Apache HTTP Server 2.4 Jeff Trawick The world of FastCGI 2014-04-10 FastCGI with Apache httpd Add Require expr ... to /www/tools/ 2.4 configuration in More classic CGI configuration Choosing slide to resolve a potential security hole. Thank mod fcgid mod proxy fcgi you Eric Covener! mod authnz fcgi Other tools PHP Applications and FastCGI Future 2/97 Get these slides... Using FastCGI with Apache HTTP Server 2.4 Jeff Trawick The world of FastCGI FastCGI with Apache httpd 2.4 http://emptyhammock.com/projects/info/slides.html Choosing mod fcgid mod proxy fcgi mod authnz fcgi Other tools PHP Applications and FastCGI Future 3/97 Table of Contents Using FastCGI with Apache HTTP Server 1 The world of FastCGI 2.4 Jeff Trawick 2 FastCGI with Apache httpd 2.4 The world of FastCGI 3 Choosing FastCGI with Apache httpd 4 mod fcgid 2.4 Choosing 5 mod proxy fcgi mod fcgid mod proxy fcgi 6 mod authnz fcgi mod authnz fcgi Other tools 7 Other tools PHP Applications 8 PHP Applications and FastCGI and FastCGI Future 9 Future 4/97 Introduction | Who am I? Using FastCGI with Apache HTTP Server 2.4 I've worked at Jeff Trawick several large corporations, for over two decades The world of FastCGI my own one-person company, Emptyhammock, for the FastCGI with last two years Apache httpd 2.4 I've worked on Choosing several products which were primarily based on or mod fcgid otherwise included Apache HTTP Server mod proxy fcgi lower-level networking products mod authnz fcgi web applications Other tools PHP I've developed or maintained some of the FastCGI Applications and FastCGI support in the Apache HTTP Server project.
    [Show full text]
  • NGINX Modules Reference
    Nginx, Inc. NGINX Plus Reference Guide NGINX Plus - release 11, based on 1.11.5 core October 19, 2016 Copyright Notice © 2012-2016 Nginx, Inc. All rights reserved. NGINX, NGINX Plus and any Nginx, Inc. product or service name or logo used herein are trademarks of Nginx, Inc. All other trademarks used herein belong to their respective owners. The trademarks and logos displayed herein may not be used without the prior written consent of Nginx, Inc. or their respective owners. This documentation is provided \AS IS" and is subject to change without notice and should not be interpreted as a commitment by Nginx, Inc. This documentation may not be copied, modified or distributed without authorization of Nginx, Inc. and may be used only in connection with Nginx, Inc. products and services. Nginx, Inc. assumes no responsibility or liability for any errors or inaccuracies that may appear in this documentation. 1 Preface About NGINX NGINX® (\engine x") is a high performance, high concurrency web server excelling at large scale content delivery, web acceleration and protecting application containers. Its precise integration with modern operating systems allows unprecedented levels of efficiency even when running on commodity hardware. Nginx, Inc. develops and maintains NGINX open source distribution, and offers commercial support and professional services for NGINX. About NGINX Plus • Offers additional features on top of the free open source NGINX version. • Prepared, tested and supported by NGINX core engineering team led by the original author Igor Sysoev. For more information • Find more details about NGINX products and support at https://www.nginx.com/. • For online NGINX documentation visit http://nginx.org/en/docs.
    [Show full text]
  • Server Side Java with Apache/Ix Page 1 of 3
    Server side Java with Apache/iX Page 1 of 3 Jazz home > Papers & Training Server side Java with » Return to original page Apache/iX (please notice that I am only tasting software, not testing it ;-) When I recently played with a trial version of Java Web Server from Sun (on MPE/iX, of course), I learned a little bit about the concept of Servlets for implementing server side functionality in Java. I found the servlet technology and associated API quite interesting, not just because of its underlying concept and architecture, but also because it allowed me -still a Java beginner- to implement a few examples of using server side Java to generate dynamic web pages with amazingly small effort. So I thought, I'd write up this little piece to share some of the experiences with you. Last, but not least, because it also can be used with Apache/iX - but we'll cover that later. What the h*** is a servlet? A servlet is basically a user-supplied extension of the web server's default functionality. Like an Applet is a piece of Java bytecode that is executed inside the web browser to implement some functionality on the client side, a Servlet is a piece of Java bytecode that is executed inside the web server to implement some functionality on the server side. In typical cases it would be used to generate web pages with dynamic content on-the-fly or provide some web interface to a server side application. The servlet technology is just another means to avoid the classic CGI child process implementation and its associated overhead for short-lived process creation as well as hassle with state management to make a sequence of inherently independent http requests form some kind of logical transaction from the user perspective.
    [Show full text]
  • Dynamic Web Content Technologies
    Dynamic web content technologies CSCI 470: Web Science • Keith Vertanen Overview • Dynamic content – What it is – Sources of input • CGI (Common Gateway Interface) – FastCGI • Server-side scripng – PHP, ASP, JSP • Web server modules • Custom web server 2 Stac vs. dynamic • Stac content – Images and pages don't change • Always the same, liKe a file server – Fast to deliver, easy to cache • Dynamic content – Same URL results in different delivered HTML • e.g. different preference on # of products to display – May change as user interac?on progresses • e.g. adding items to a shopping cart – Need something besides just HTTP and HTML • HTTP is stateless • HTML is not programmable (e.g. condi?onal, loops) 3 Input to dynamic pages • Form fields – <INPUT> tags inside the <FORM> tag – URL encoding (percent-encoded) • if GET: in the URL, if POST: in the HTTP payload • Unreserved characters: – ABCDEFGHIJKLMNOPQRSTUVWXYZ abcdefghijKlmnopqrstuvwxyz0123456789-_.~ • Reserved characters: – !*'();:@&=$,/?#[] – Converted to %XX, where XX is ASCII in hexadecimal – %20 = space (also +), %21 = !, %23 = #, %25 = %, … • Most languages have URL encode/decode func?ons 4 Input to dynamic pages • Cookies – Differen?ate clients hing same page • Other input sources: – User agent (browser) – HTTP referer • Misspelled since original RFC 1945 • The page you came from to get to this one – Client's IP address – Time of day – … 5 CGI • CGI (Common Gateway Interface) – In use since 1993 – Requests a URL in a special locaon/file extension • e.g. h~p://www.blah.com/cgi-bin/looKup
    [Show full text]
  • Fastcgi 1 Fastcgi
    FastCGI 1 FastCGI FastCGI es un protocolo para interconectar programas interactivos con un servidor web. FastCGI es una variación de la ya conocida Common Gateway Interface (CGI ó Interfaz Común de Entrada). El principal objetivo de FastCGI es reducir la carga asociada con el hecho de interconectar el servidor web y los programas Common Gateway Interface, permitiéndole a un servidor atender más peticiones a la vez. Ventajas • Independencia del lenguaje utilizado. Libertad de elección de la plataforma de desarrollo: C++, PHP, Perl, Java, entre otros. • Se utiliza un proceso separado. Libertad de elección del servidor web. Facilidad para el tratamiento de errores y depuración. • Es posible la ejecución en host separado. Mayor libertad para configuración del sistema, tanto en el diseño de la red como en la elección de los sistemas operativos. Disminución de la carga de trabajo del servidor principal. En resumen, la libertad de diseño de CGI a la velocidad de un módulo del servidor.. Historia CGI es un protocolo para interconectar aplicaciones externas con servidores web. Las aplicaciones CGI corren en un proceso separado que es creado al inicio de cada petición y es finalizado cuando termina su trabajo. Este modelo de "un nuevo proceso por cada petición" hace que los programas CGI sean muy fáciles de implementar, pero limita la eficiencia y la escalabilidad. En altas cargas, la sobrecarga en el sistema operativo por la creación y destrucción de procesos se torna significativa y limita la escalabilidad. Además, el modelo de procesos CGI limita las técnicas de reutilización de recursos (como ser la reutilización de conexiones a base de datos, caché en memoria, etc).
    [Show full text]
  • Fifty-Year Anniversaries in Norwegian Computing History
    EVENTS AND SIGHTINGS Editor: Chigusa Kita Fifty-Year Anniversaries in Norwegian Computing History wo fifty-year anniversaries in computing history were celebrated in Oslo in September 2017: the fifty-year T anniversary of the creation of the Simula program- ming language, and the fifty-year anniversary of the found- ing of the Norsk Data computer company. Simula The Simula 67 programming language, first formally defined in 1967, was a step in a series of developments by Ole-Johan Dahl and Kristen Nygaard that began in the early 1960s.1 Dahl and Nygaard were given the 2001 IEEE John von Neumann Medal and the ACM 2001 A.M. Turing Award for their creation of Simula. A fifty-year anniversary celebration for Simula took place (in the “Simula Auditorium” in the “Ole-Johan Dahl Building”) at the University of Oslo on 27 September 2017. PHOTO 1. Photo credit: Harald Brombach/digi.no. The celebration began with unveiling of a plaque from the IEEE History Committee’s Milestone program. The plaque reads: chaired by Eric Jul (“Whither Programming Languages? Can IEEE Milestone We Still Celebrate Simula 50 Years from Now?”) with partic- Object-oriented Programming, 1961–1967 ipation of the prior three speakers and Ole Lehrmann Mad- Ole-Johan Dahl and Kristen Nygaard created the sen and Olaf Owe.2 Videos from the event are available.3 Simula programming languages in the 1960s at the The previous afternoon, the Association of Simula Norwegian Computer Center, and in so doing intro- Users (ASU) held a several-hour meeting at which there duced a new way of modeling and simulating complex were six presentations and a wrap-up session.
    [Show full text]