DOCSLIB.ORG

Fastcgi 1 Fastcgi

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read 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). Para encarar el problema de escalabilidad del CGI, Open Market desarrolló FastCGI y lo introdujo por primera vez en su producto de servicio web a mediados de los 90'. Open Market originalmente desarrolló FastCGI en parte como una respuesta competitiva contra la, en aquel entonces en proceso, API propietaria de Netscape's, la NSAPI que servía para desarrollar aplicaciones Web. Aunque inicialmente desarrollada por Open Market, FastCGI fue implementada por otros fabricantes de servicios web. FastCGI, sin embargo, compitió contra otras técnicas que también intentaban aumentar la velocidad y simplificar las comunicaciones del lado del servidor, pero sin seguir el paradigma CGI. Módulos para Apache tales como mod perl y mod php aparecieron aproximadamente por la misma fecha y parecían ser mejores reemplazos para CGI, permitiendo una integración muy próxima con la base del servidor web. Detalles de la implementación En vez de crear procesos nuevos por cada petición, FastCGI puede usar un solo proceso persistente el cual maneja cualquier petición durante su período de vida. El hecho de procesar múltiples peticiones a la vez es logrado ya sea mediante la utilización de una sola conexión con un multiplexado interno (por ejemplo múltiples peticiones sobre una sola conexión) y/o utilizando múltiples conexiones. Varios de esos procesos pueden existir, y eso es algo que incrementa la escalabilidad y el rendimiento. FastCGI permite también a los programas hacer que el servidor web realice ciertas operaciones sencillas, como leer un archivo antes de que la petición sea procesada. Las variables de entorno y las peticiones de páginas son enviadas desde el servidor web hacia los procesos a través de una conexión TCP (para procesos remotos) o a través de zócalos de Unix (para procesos locales). Las respuestas son devueltas desde el proceso hacia el servidor web sobre la misma conexión. La conexión puede ser cerrada al final de una respuesta, pero el servidor web y el proceso se mantienen en ejecución. FastCGI 2 Varios administradores y programadores de sitios web encontraron que la separación de las aplicaciones web con respecto al servidor web producto de FastCGI (y la simplicidad de SCGI) tenían muchas ventajas sobre los intérpretes incrustados (mod perl, mod php, etc). Esta separación permite a los procesos del servidor y de las aplicaciones ser reiniciados en forma independiente; una consideración importante a tomar en cuenta en sitios web muy ocupados. Esto también facilita la aplicación de políticas de seguridad por cada aplicación; cosa importante para los ISPs y para las compañías de alojamiento web. Servidores Web que implementan FastCGI Nota: a menos que se notifique lo contrario, hasta ahora no se sabe cuándo será completada la implementación FastCGI • Abyss Web Server • Apache HTTP Server (parcial) • Implementado por mod_fcgid [1]. Este módulo era de terceros, pero fue garantizado que sería un subproyecto de Apache en el 2009, liderado por Chris Darroch[2] • El módulo desactualizado de terceros mod_fastcgi también está siendo utilizado • Multiplexado de peticiones a través de una sola conexión está prohibido por el diseño de Apache,[3] así que no está soportado en Apache • Cherokee HTTP Server[4] • Hiawatha webserver[5] • Soporte de balance de carga para FastCGI • Soporte servidores FastCGI con jaula root • Lighttpd[6] • Monkey Web Server[7] • LiteSpeed Web Server • Microsoft IIS[8] • Kerio WebSTAR • Nginx • Open Market Web Server • Resin Application Server • Roxen Web Server • Sun Java System Web Server • Cualquier contenedor Servlet (como ser Apache Tomcat o Jetty), usando la biblioteca JFastCGI [9]. • Zeus Web Server • My server project 'Bindings' de lenguajes para la API FastCGI FastCGI puede ser implementado en cualquier lenguaje que soporte zócalos (sockets). La API existe[10] para: • Borland Delphi/FreePascal[11] • C • C++ • Chicken Scheme • Common Lisp: CLISP y CMUCL • D • Guile Scheme • Eiffel[12] FastCGI 3 • Haskell • HP BASIC for OpenVMS • Java • Lua • OCaml • Mono XSP • Perl[13] • PHP • Roadsend PHP • Python • Ruby • SmallEiffel • Smalltalk: FasTalk and Dolphin Smalltalk • TCL FastCGI permitió portabilidad a las aplicaciones web; en contraste, las aplicaciones que fueron desarrolladas para intérpretes embebidos (tales como mod python) están generalmente muy limitadas a la API de Apache. Frameworks recientes tales como Ruby on Rails, Kepler (etc...) permiten el uso de cualquiera de los intérpretes embebidos (mod ruby, mod perl, mod python o mod_lual, respectivamente), pero también FastCGI. Esta tendencia parece ser que va a continuar. Bibliotecas que incluyen soporte para FastCGI • qDecoder [14] • GNU Cgicc [15] Referencias [1] http:/ / httpd. apache. org/ mod_fcgid/ [2] FastCGI apache module mod_fcgid (http:/ / httpd. apache. org/ mod_fcgid/ ) [3] FastCGI – The Forgotten Treasure/ Section 2.3. (http:/ / cryp. to/ publications/ fastcgi/ #AEN147) [4] FastCGI for Cherokee (http:/ / www. cherokee-project. com/ doc/ modules_handlers_fcgi. html) [5] FastCGI HOWTO for Hiawatha (http:/ / www. hiawatha-webserver. org/ howto/ #5. 1) [6] FastCGI for Lighttpd (http:/ / trac. lighttpd. net/ trac/ wiki/ Docs:ModFastCGI) [7] FastCGI for Monkey Web Server (http:/ / monkey-project. com/ about) [9] https:/ / sourceforge. net/ projects/ jfastcgi [10] Application Libraries / Development Kits (http:/ / www. fastcgi. com/ drupal/ node/ 5) [11] ExtPascal (http:/ / extpascal. googlecode. com) [12] Goanna Eiffel (http:/ / goanna. origo. ethz. ch) [13] Hay varios módulos FastCGI para Perl: FCGI (http:/ / search. cpan. org/ perldoc?FCGI) (un módulo compilado escrito en C), FCGI::Async (http:/ / search. cpan. org/ perldoc?FCGI::Async) (de aplicaciones FastCGI asíncronas), AnyEvent::FCGI (http:/ / search. cpan. org/ perldoc?AnyEvent::FCGI) (para aplicaciones AnyEvent (http:/ / search. cpan. org/ perldoc?AnyEvent)-basadas en), FCGI::EV (http:/ / search. cpan. org/ perldoc?FCGI::EV) (para aplicaciones EV (http:/ / search. cpan. org/ perldoc?EV)-basadas en), CGI::Fast (http:/ / search. cpan. org/ perldoc?CGI::Fast) (Perl similar CGI (http:/ / search. cpan. org/ perldoc?CGI)-interface para FastCGI), FCGI::Client (http:/ / search. cpan. org/ perldoc?FCGI::Client) (una biblioteca de cliente FastCGI), y Net::FastCGI (http:/ / search. cpan. org/ perldoc?Net::FastCGI) (constantes y funciones para construir y analizar mensajes FastCGI). [14] http:/ / www. qdecoder. org/ [15] http:/ / www. gnu. org/ software/ cgicc/ FastCGI 4 Bibliografía • Sergio Luján Mora (2001) (en español, libro completo gratuito en pdf). Programación de servidores web con CGI, SSI e IDC (http:/ / hdl. handle. net/ 10045/ 16997) (1ª edición). Editorial Club Universitario. Enlaces externos • Página Inicial de FastCGI (http:/ / www. fastcgi. com) (inglés) • FastCGI specification (http:/ / www. fastcgi. com/ devkit/ doc/ fcgi-spec. html) • mod_fastcgi – FastCGI module for Apache 1.x and 2.x supporting external applications (http:/ / www. fastcgi. com/ mod_fastcgi/ docs/ mod_fastcgi. html) • mod_fcgid - a FastCGI module for Apache 2.x (http:/ / httpd. apache. org/ mod_fcgid/ ) • Microsoft FastCGI (http:/ / www. iis. net/ default. aspx?tabid=1000051) • Apache v2.x mod_proxy FastCGI Module (http:/ / mproxyfcgi. sourceforge. net/ ) • FastCGI interface for WASD httpd server for OpenVMS (http:/ / wasd. vsm. com. au/ ht_root/ src/ fcgi/ readmore. html) • FastCGI y PHP seguro en UserDir (http:/ / anyeos. wordpress. com/ 2008/ 07/ 18/ fastcgi-y-php-seguro-en-userdir) Fuentes y contribuyentes del artículo 5 Fuentes y contribuyentes del artículo FastCGI Fuente: http://es.wikipedia.org/w/index.php?oldid=67955584 Contribuyentes: Ajavier, Cristo Manco, Dianai, Dodo, Hcastillo, Hyperspeed, John plaut, Poco a poco, Qwertyytrewqqwerty, Serlumo, Sonia Rod, SpeedyGonzalez, Superzerocool, Wiyarmir, 45 ediciones anónimas Licencia Creative Commons Attribution-Share Alike 3.0 Unported //creativecommons.org/licenses/by-sa/3.0/.
Load more

Recommended publications
  • 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]
  • A Systematic Review of Web Server Technologies Brixton Hamilton
    A Systematic Review of Web Server Technologies Brixton Hamilton Abstract The choice between different web server technologies is an increasingly relevant problem that users must face. This article will outline the features and functionalities that web servers perform, the differences between them, focusing on Apache, IIS, Jetty and Nginx, and how those relate to the requirements of different users. I will analyse the current trends in web server technologies, and suggest how they might continue to change in the future. As the internet rapidly grows and evolves, so must the web server technologies we use to host the websites on it. From merely tens of thousands of sites predominantly using NCSA server technology shortly after the birth of the internet, as of November 2016 there are 171 Million active sites[1], and over time the ever-changing needs of these sites will need to be met by more suitable web servers. The role of the web server in isolation is clear-cut, it must handle HTTP requests. However, outside this it must work with database systems (such as MySQL or MongoDB), serve dynamic content using server-side scripting languages (e.g. PHP or ASP .NET), and deal with the operating system on which it runs (most commonly Linux). Many different web server technologies exist, and when choosing between them, compatibility with the other elements of your server architecture is important. For the past 20 years, the clear-cut leader for active websites has been Apache, an adaptable, open- source server, usually run alongside Linux, PHP and MySQL as part of a ‘LAMP Stack’.
    [Show full text]
  • A Brief Review of Speech Synthesis
    Computer Science Computer Networks Piotr Leszczyński Book No. s4207 Remote voice Web browser for people with sight impairment Zdalna głosowa przeglądarka WWW dla osób niewidomych Engineering Thesis Written under the advice of Ph.D. Eng. Przemysław Skurowski Bytom September 2009 Contents 1 Introduction............................................................................... 7 2 A brief review of speech synthesis ................................................ 9 2.1 Human speech synthesis ......................................................... 9 2.2 Text-To-Speech systems overview .......................................... 10 2.2.2 Concatenation Speech Systems ...................................... 11 2.2.3 Articulator Speech Systems ............................................ 11 2.2.4 History ........................................................................ 12 3 Application modeling and implementation .................................... 14 3.1 Application concept ............................................................... 14 3.2 Functional requirements ........................................................ 15 3.3 Non-Functional requirements ................................................. 16 3.4 Feasibility analysis ................................................................ 16 3.5 Technical limitations ............................................................. 17 3.5.1 Accessibility ................................................................. 17 3.5.2 Speech synthesis .........................................................
    [Show full text]
  • O'reilly® Jason Hunter
    rr Help for Server-Side Java Developer, '" Jason Hunter O'REILLY® with William Crawford Page 1 of 94 J ava" Servlet Programming Page 2 of 94 THE JAVA"" SERIES Learning Java m Java'" Performance Tuning Java'" Threads Java'" Internationalization Java'· Network Programming JavaServer Pages" Database Programming with JDBC'Mand Java'" Java m Message Service Java'" Distributed Computing Developing Java Beans'M Java" Security Java" Cryptography Also from O'Reilly Java" Swing Java" Servlet Programming Java'M in a Nutshell Java" I/O J ava" Enterprise in a Nutshell J ava™ 2D Graphics Java'" Foundation Classes in a Nutshell Enterprise Javafleans" Java" Examples in a Nutshell Creating Effective JavaHelp'M JiniTM in a Nutshell Java'" and XML The Enterprise Java" CD Bookshelf Page 3 of 94 -, Javan, Servlet Programming Second Edition Jason Hunter with William Crawford O'REILLY® Beijing. Cambridge. Farnham» Koln » Paris > Sebastopol. Taipei. Tokyo Page 4 of 94 Java Servlet Programming, Second Edition byJason Hunter with William Crawford Copyright © 2001,1998 O'Reilly & Associates, Inc. All rights reserved. Printed in the United States of America. Published by O'Reilly & Associates, Inc., 101 Morris Street, Sebastopol, CA 95472. Editors: Robert Eckstein and Paula Ferguson Production Editor: Colleen Gorman Cover Designer: Hanna Dyer Printing History: October 1998: First Edition. April 2001: Second Edition. Nutshell Handbook, the Nutshell Handbook logo, and the O'Reilly logo are registered trademarks and The Java™ Series is a trademark of O'Reilly & Associates, Inc. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this book, and O'Reilly & Associates, Inc.
    [Show full text]
  • GNU/Linux Magazine Hors-Série N°66 Apache Introduction
    LES GUIDES DE sur les origines d Ce documntslapriéxvj-g(@h.)26013à:5 Tout ce qu LE GUIDE COMPLET POUR METTRE EN PLACE ET BIEN CONFIGURER VOTRE SERVEUR WEB APACH France METRO : 12.90 et sur ses principales Introduction fonctionnalités il faut savoir Apache CH : 18,00 CHF Installation et con Installer son premier BEL/PORT.CONT : 13,90 serveur et choisir le mécanisme d plus adapté authenti HORS-SÉRIE guration ���� cation le DOM TOM : 13,90 Programmer pour le Web PHP, Python, Perl et Ruby : quelques bases pour bien programmer avec les langages du Web CAN : 18,00 $ cad Aller plus loin MAR : 130 MAD Des éléments de con pour des besoins plus spéci (LDAP, chi guration avancée ques L 15066 ff Édité par Les Éditions Diamond Éditions Les par Édité rement, ...) www.ed-diamond.com -66H F: Tutoriels Des pas-à-pas 12,90 pour passer E rapidement à la pratique € -RD Ce documntslapriéxvj-g(@h.)26013à:5 2 GNU/LiNUx maGaziNeHors-série N°66 : apacHe Impression : Service abonnement: Responsable publicité: Conception graphique: Remerciements Secrétaire derédaction Rédacteur enchef: Directeur depublication: Sites : Service commercial: E-mail : Tél. : est éditépar GNU/Linux MagazineHors-Série Éditions Diamond. rédigés parlesmembresdel'équiperédactionnelledes Les articlesnonsignéscontenusdanscenuméroontété respectif. droit ayant leur de propriété sont la dans le magazine les représentés logos Tous respectif. citées dans ce numéro sont déposées par les sans aucun marques Toutes d’information, but publicitaire. leur propriétaire figurant dans d’adresses les et prix pages de sont rédactionnelles indications données Les à renvoyés. titre ni rendus, ni sont GNU/Linux Magazine France Hors-série, publiés ou non, ne particulier, les manuscrits, photos accord écrit et de la société Les éditions Diamond.
    [Show full text]
  • X-Switch: an Efficient, Multi-User, Multi-Language Web Ap- Plication Server
    Research Article | SACJ, Submission, 2009 1 X-Switch: An Efficient, Multi-User, Multi-Language Web Ap- plication Server Mayumbo Nyirenda, Hussein Suleman, Andrew Maunder, Reinhardt van Rooyen Department of Computer Science, University of Cape Town ABSTRACT Web applications are usually installed on and accessed through a Web server. For security reasons, these Web servers generally provide very few privileges to Web applications, defaulting to executing them in the realm of a guest account. In addition, performance often is a problem as Web applications may need to be reinitialised with each access. Various solutions have been designed to address these security and performance issues, mostly independently of one another, but most have been language or system-specific. The X-Switch system is proposed as an alternative Web application execution environment, with more secure user-based resource management, persistent application interpreters and support for arbitrary languages/interpreters. Thus it provides a general-purpose environment for developing and deploying Web applications. The X-Switch system's experimental results demonstrated that it can achieve a high level of performance. Furthermore it was shown that X-Switch can provide functionality matching that of existing Web application servers but with the added benefit of multi-user support. Finally the X-Switch system showed that it is feasible to completely separate the deployment platform from the application code, thus ensuring that the developer does not need to modify his/her code to make it compatible with the deployment platform. KEYWORDS: Web application servers, scalability, context switching, process persistence, modularity 1 INTRODUCTION in Java, another in PHP and a third in Perl, it is non-trivial (if at all possible) to have a single Web Web applications that once were fairly monolithic are server software system cater for all languages and, ad- slowly making the transition to collections of cooper- ditionally, keep all interpreters and virtual machines ating services.
    [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]
  • Etude Des Facteurs De Succès Du Projet Open Source Apache HTTP
    Etude des facteurs de succès du projet open source Apache HTTP Dr Ir Robert Viseur * ** * CETIC, Avenue Jean Mermoz, 28, B-6041 Charleroi ** UMONS Faculté Polytechnique, Rue de Houdain, 9, B-7000 Mons [email protected], [email protected] Résumé : Avec Linux, Firefox et OpenOffice.org, le projet Apache HTTP fait partie des success stories populaires dans le domaine open source. Dans cette recherche, nous proposons d’explorer les facteurs de succès qui ont permis au serveur web Apache HTTP de devenir un projet open source mondial et pérenne. Après une étude longitudinale du projet identifiant les facteurs de succès, nous discutons différents apprentissages à l’usage des gestionnaires et développeurs de projets collaboratifs. Mots clés : logiciel libre, open source, serveur web, apache, utilisateur de pointe, world wide web. 1 Study of success factors for the Apache HTTP open source project Dr Ir Robert Viseur * ** * CETIC, Avenue Jean Mermoz, 28, B-6041 Charleroi ** UMONS Faculté Polytechnique, Rue de Houdain, 9, B-7000 Mons [email protected], [email protected] Abstract With Linux, Firefox and OpenOffice.org, Apache HTTP project is one of the popular success stories in the open source sector. In this research, we propose to explore the success factors that enabled Apache HTTP Web server to become a wordlwide and sustainable open source project. After a longitudinal study of the project identifying success factors, we discuss different findings for managers and developers aiming to set up collaborative projects. Keywords free software, open source, web server, apache, lead user, world wide web. 2 Introduction Le serveur web Apache HTTP, avec sa part de marché fréquemment supérieure à 50%, est un des logiciels open source incontournables.
    [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]
  • Comparison of Web Server Software from Wikipedia, the Free Encyclopedia
    Create account Log in Article Talk Read Edit ViewM ohrisetory Search Comparison of web server software From Wikipedia, the free encyclopedia Main page This article is a comparison of web server software. Contents Featured content Contents [hide] Current events 1 Overview Random article 2 Features Donate to Wikipedia 3 Operating system support Wikimedia Shop 4 See also Interaction 5 References Help 6 External links About Wikipedia Community portal Recent changes Overview [edit] Contact page Tools Server Developed by Software license Last stable version Latest release date What links here AOLserver NaviSoft Mozilla 4.5.2 2012-09-19 Related changes Apache HTTP Server Apache Software Foundation Apache 2.4.10 2014-07-21 Upload file Special pages Apache Tomcat Apache Software Foundation Apache 7.0.53 2014-03-30 Permanent link Boa Paul Phillips GPL 0.94.13 2002-07-30 Page information Caudium The Caudium Group GPL 1.4.18 2012-02-24 Wikidata item Cite this page Cherokee HTTP Server Álvaro López Ortega GPL 1.2.103 2013-04-21 Hiawatha HTTP Server Hugo Leisink GPLv2 9.6 2014-06-01 Print/export Create a book HFS Rejetto GPL 2.2f 2009-02-17 Download as PDF IBM HTTP Server IBM Non-free proprietary 8.5.5 2013-06-14 Printable version Internet Information Services Microsoft Non-free proprietary 8.5 2013-09-09 Languages Jetty Eclipse Foundation Apache 9.1.4 2014-04-01 Čeština Jexus Bing Liu Non-free proprietary 5.5.2 2014-04-27 Galego Nederlands lighttpd Jan Kneschke (Incremental) BSD variant 1.4.35 2014-03-12 Português LiteSpeed Web Server LiteSpeed Technologies Non-free proprietary 4.2.3 2013-05-22 Русский Mongoose Cesanta Software GPLv2 / commercial 5.5 2014-10-28 中文 Edit links Monkey HTTP Server Monkey Software LGPLv2 1.5.1 2014-06-10 NaviServer Various Mozilla 1.1 4.99.6 2014-06-29 NCSA HTTPd Robert McCool Non-free proprietary 1.5.2a 1996 Nginx NGINX, Inc.
    [Show full text]