DOCSLIB.ORG

Storefront 1903

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Storefront 1903 StoreFront 1903 Citrix Product Documentation | docs.citrix.com June 10, 2019 StoreFront 1903 Contents StoreFront 1903 3 What’s new 4 Fixed issues 5 Known issues 7 Third party notices 7 System requirements 7 Plan your StoreFront deployment 15 User access options 20 User authentication 29 Optimize the user experience 41 StoreFront high availability and multi-site configuration 46 Install, set up, upgrade, and uninstall 50 Create a new deployment 62 Join an existing server group 68 Reset a server to factory defaults 69 Migrate Web Interface features to StoreFront 71 Configure server groups 77 Configure authentication and delegation 80 Configure the authentication service 81 XML service-based authentication 89 Configure Kerberos constrained delegation for XenApp 6.5 89 Configure smart card authentication 93 Configure the password expiry notification period 98 © 1999-2019 Citrix Systems, Inc. All rights reserved. 2 StoreFront 1903 Configure and manage stores 99 Create or remove a store 100 Create an unauthenticated store 106 Export store provisioning files for users 108 Advertise and hide stores to users 109 Manage the resources made available in stores 110 Manage remote access to stores through Citrix Gateway 111 Configure two StoreFront stores to share a common subscription datastore 114 Manage subscription data for a store 116 Advanced store settings 122 Manage a Citrix Receiver for Web site 127 Create a Citrix Receiver for Web site 128 Configure Citrix Receiver for Web sites 129 Support for the unified user experience 135 Create and manage featured apps 140 Configure workspace control 142 Configure Citrix Workspace app for HTML5 use of browser tabs 143 Configure communication timeout duration and retry attempts 143 Configure user access 145 Configure StoreFront to launch applications and desktops in Windowed Mode 149 Set up highly available multi-site stores 150 Force connections through Citrix Gateway using Optimal Gateway feature of StoreFront 167 Integrate with Citrix Gateway and Citrix ADC 169 Add a Citrix Gateway connection 171 © 1999-2019 Citrix Systems, Inc. All rights reserved. 3 StoreFront 1903 Import a Citrix Gateway 174 Configure Citrix Gateway connection settings 184 Load balancing with Citrix ADC appliance 187 Configure two URLs for the same Citrix Gateway 206 Configure Citrix ADC and StoreFront for Delegated Forms Authentication (DFA) 217 Authenticate using different domains 220 Configure beacon points 230 Create a single Fully Qualified Domain Name (FQDN) to access a store internally and exter- nally 232 Advanced configurations 250 Configure Desktop Appliance sites 251 Configure Resource Filtering 255 Configure using configuration files 256 Configure StoreFront using the configuration files 257 Configure Citrix Receiver for Web sites using the configuration files 261 Secure your StoreFront deployment 263 Export and import the StoreFront configuration 270 StoreFront SDK 280 Troubleshoot StoreFront 296 © 1999-2019 Citrix Systems, Inc. All rights reserved. 4 StoreFront 1903 StoreFront 1903 March 28, 2019 StoreFront 1903 is the latest Current Release version of StoreFront. This documentation reflects fea- tures and configurations in this latest release. StoreFront is an enterprise app store that aggregates applications and desktops from Citrix Virtual Apps and Desktops sites into a single easy to use store for users. StoreFront is an integral component of Citrix Virtual Apps and Desktops (formerly XenApp and XenDesktop) but can be used with several versions of Virtual Apps and Desktops. Users can work with Citrix Workspace app or supported versions of Citrix Receiver to access StoreFront stores. If a specific version behaves differently or the user interface text refers to both, it will be called out, otherwise the documentation refers to “Citrix Workspace app”. Earlier releases For documentation on previous releases, see: • StoreFront 1811 • StoreFront 3.16 • StoreFront 3.15 • StoreFront 3.14 • StoreFront 3.13 • StoreFront 3.12 • Earlier StoreFront versions The product lifecycle strategy for Citrix Virtual Apps and Desktops Current Releases (CR) and Long Term Service Releases (LTSR) is described in Lifecycle Milestones. Additional Lifecycle Information for StoreFront is provided in CTX200356. Note: Upgrades to the latest Current Release version of StoreFront from earlier unsupported versions is not supported. If you are using Current Releases you must ensure that you are on a supported StoreFront Current Release version at all times. Citrix product name and version number changes If you’ve been a Citrix customer or partner for a while, you’ll notice new names in our products and in this product documentation. If you’re new to this Citrix product, you might see different names for © 1999-2019 Citrix Systems, Inc. All rights reserved. 5 StoreFront 1903 a product or component. The new product and component names stem from the expanding Citrix portfolio and cloud strategy. To learn about how recent name changes affect StoreFront, see New product names. What’s new March 28, 2019 StoreFront 1903 StoreFront 1903 includes the following new features. For information about bug fixes, see Fixed issues. Removal of classic user experience The classic user experience (“green bubbles”) was announced as deprecated at XenApp and Xen Desk- top 7.15 LTSR, and it is no longer supported in StoreFront 1903 (Citrix Virtual Apps and Desktops 7 1903). When you upgrade to StoreFront 1903, stores which were using the classic experience are changed to the unified experience. The unified experience delivers a centrally managed HTML5 user experience to the web and to native Citrix Workspace apps (formerly Citrix Receiver), together with customiza- tion and featured app groups management. For more information about the unified experience, see Unified user experience. New product names If you’ve been a Citrix customer or partner for a while, you’ll notice new names in our products and in this product documentation. If you’re new to this Citrix product, you might see different names for a product or component. The new product and component names stem from the expanding Citrix portfolio and cloud strategy. Implementing this transition in our products and their documentation is an ongoing process. • In-product content might still contain former names. For example, you might see instances of earlier names in console text, messages, and directory/file names. • It is possible that some items (such as commands and MSIs) might continue to retain their for- mer names to prevent breaking existing customer scripts. • Related product documentation and other resources (such as videos and blog posts) that are linked from this product’s documentation might still contain former names. © 1999-2019 Citrix Systems, Inc. All rights reserved. 6 StoreFront 1903 • In this StoreFront documentation, mentions of “Citrix Workspace app” also represent the sup- ported versions of Citrix Receiver unless otherwise noted. Your patience during this transition is appreciated. For more detail about our new names, see https: //www.citrix.com/about/citrix-product-guide/. Management console and documentation product name changes Text in the StoreFront management console has been updated to the new Citrix product names. Ref- erences to removed functionality and products, which are described in the Citrix Virtual Apps and Desktops Deprecation article, are also removed. For example, references to “NetScaler Gateway” are now “Citrix Gateway”,and references to “Citrix Receiver” are now “Citrix Workspace app”. Please note that the term “Citrix Receiver for Web site” is unchanged, and still refers to a website used as an app store. The StoreFront product documentation is updated to match text in the StoreFront management con- sole, and the new Citrix product names. Deprecation of TLS versions The deprecation of StoreFront support for TLS 1.0 and 1.1 protocols was announced at StoreFront 3.14 and XenApp and XenDesktop 7.17, see CTX232266. Customers can now also upgrade to Citrix Workspace app, which supports the TLS 1.2 protocol. At StoreFront 1903, Citrix further recommends disabling TLS 1.0 and 1.1 support in the Web Server hosting StoreFront. You should enforce this via group policy objects, which create the necessary reg- istry settings on the StoreFront server to disable older protocols like TLS 1.0 and TLS 1.1. See also the Microsoft TLS/SSL Settings reference topic. Fixed issues March 28, 2019 The following issues have been fixed since version 1811: • Uninstalling StoreFront on Windows Server 2019 can result in the PowerShell console (Power- shell.exe) no longer running on the server. The symptoms are that Powershell.exe opens briefly then vanishes immediately and cannot be used. Powershell_ISE.exe is unaffected and can still be used to run Powershell scripts. [STF-2585] © 1999-2019 Citrix Systems, Inc. All rights reserved. 7 StoreFront 1903 • The StoreFront management console does not allow keywords ExcludeMe and IncludeMe to be set together. Either keyword can be set but as soon as you attempt to set the other, the first keyword is removed by the console. [STF-3388] • The StoreFront management console permits you to use the prohibited underscore character (_) in a Base URL. This makes stores inaccessible as DNS does not support the use of underscores. [STF-3509] • Receiver for Web becomes unusable if you use the StoreFront PowerShell SDK to set both Ex- clude and Include keywords for resource filtering. [STF-3208] • When a desktop contains an ampersand (&) character in its
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]
  • 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]
  • 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]
  • C Server Pages: an Architecture for Dynamic Web Content Generation
    C Server Pages: An Architecture for Dynamic Web Content Generation John Millaway Phillip Conrad Dept. of Computer and Information Sciences Dept. of Computer and Information Sciences Temple University Temple University 1805 N. Broad St. 1805 N. Broad St. Philadelphia, PA 19122 Philadelphia, PA 19122 [email protected] [email protected] ABSTRACT curs heavyweight process creation overhead. Approaches that in- This paper introduces C Server Pages (CSP), a highly efficient ar- volve simple template substitution by the web server itself based on chitecture for the creation and implementation of dynamic web so called server-side includes (SSIs) are lightweight, but not very pages. The CSP scripting language allows dynamic web contents to powerful. Application servers such as ColdFusion [3] introduce a be expressed using a combination of C code and HTML. A novel heavyweight run time layer. Interpreted languages such as Java, feature of CSP is that the C portions of the CSP source file are PHP, and Perl are typically slower than compiled languages such compiled into dynamic load libraries that become part of the run- as C. New languages specifically designed for the generation of ning web server, thus avoiding both the overhead of interpreted lan- server side content present an additional learning curve for already guages such as Perl, Java and PHP, as well as the need to create a overburdened developers [8]. separate process. We present an overview of the architecture and This paper introduces an alternative architecture called C Server implementation, and provide results of performance benchmarks Pages (CSP), based on combining languages familiar to many de- showing that CSP outperforms similar mainstream technologies, velopers: HTML, and C.
    [Show full text]
  • Server Side Programming
    SAN DIEGO COMMUNITY COLLEGE DISTRICT CONTINUING EDUCATION COURSE OUTLINE SECTION I SUBJECT AREA AND COURSE NUMBER COMP 623 COURSE TITLE SERVER SIDE PROGRAMMING TYPE COURSE NON-FEE VOCATIONAL CATALOG COURSE DESCRIPTION In this course students will learn how to deliver dynamic content on Web sites. This course covers Server Side programming, (such as ASP.NET, CGI, Java VM, MySQL, and Fast CGI). Students will also learn about extending Web server software through configuring and scripting. (FT) LECTURE/LABORATORY HOURS 250 ADVISORY NONE RECOMMENDED SKILL LEVEL Possess a 10th grade reading level; ability to communicate effectively in the English language; knowledge of math concepts at the 8th grade level; ability to use a mouse, menus, open and close windows and save files within the Macintosh or Windows operating system; and ability to use an internet browser. INSTITUTIONAL STUDENT LEARNING OUTCOMES 1. Social Responsibility SDCE students demonstrate interpersonal skills by learning and working cooperatively in a diverse environment. 2. Effective Communication SDCE students demonstrate effective communication skills. CEISO 02/07; Revised 12/18/13 SERVER SIDE PROGRAMMING PAGE 2 INSTITUTIONAL STUDENT LEARNING OUTCOMES (CONTINUED) 3. Critical Thinking SDCE students critically process information, make decisions, and solve problems independently or cooperatively. 4. Personal and Professional Development SDCE students pursue short term and life-long learning goals, mastering necessary skills and using resource management and self advocacy skills to cope with changing situations in their lives. COURSE GOALS To provide instruction in how dynamic content is delivered on the Web. Students will learn about Server-Side includes, the Common Gateway Interface (CGI), and about writing and debugging CGI scripts.
    [Show full text]
  • Metaprogramming for the Web? (Newbie Intro to OSIS2016 “State of the Art Web Technologies” Workshop)
    metaprogramming for the Web? (newbie intro to OSIS2016 “state of the art web technologies” workshop) Basile STARYNKEVITCH gcc-melt.org and starynkevitch.net/Basile/ [email protected] or [email protected] CEA, LIST (Software Reliability Lab.), Palaiseau, France [within Université Paris Saclay] June 28th, 2016, Open Source Innovation Spring, Jussieu, Paris, France Basile Starynkevitch metaprogramming for the Web? June 28th, 2016 (OSIS2016) ? 1 / 18 Overview 1 Introduction 2 [Meta-] programming for the web 3 A few newbie technical questions Slides available at starynkevitch.net/Basile/starynkevitch-osis2016.pdf under (Creative Commons Attribution Share Alike 4.0 International license) LATEX/ Beamer source code on github.com/bstarynk/osis2016webtech/ All opinions are mine only Basile Starynkevitch metaprogramming for the Web? June 28th, 2016 (OSIS2016) ? 2 / 18 Introduction 1 Introduction 2 [Meta-] programming for the web 3 A few newbie technical questions Basile Starynkevitch metaprogramming for the Web? June 28th, 2016 (OSIS2016) ? 3 / 18 Introduction Introduction (audience) Expected audience (OSIS2016) : developers curious of Web technologies web developers curious on non-mainstream Web technologies free-software friendly and knowledgable Basile Starynkevitch metaprogramming for the Web? June 28th, 2016 (OSIS2016) ? 4 / 18 Introduction Why am I (Basile) interested by web technologies? I am a compiler & static source code analysis guy (gcc-melt.org), very far from the Web! Web technologies are about half of IT economy static
    [Show full text]
  • A Comparison of Portable Dynamic Web Content Technologies for the Apache Server
    A Comparison of Portable Dynamic Web Content Technologies for the Apache Server December 16, 2012 1 Introduction Dynamic web content typically entails user input on a web page processed by the server to affect the generation of a corresponding new page. In most applications the server- side processing is the key to the whole process. The web server is responsible for handling user input, start a program that processes it (or just pass it to an already running program), get the results and send them back to the user. The processing program often communicates with a database to find stored information and keeps session data to remember the user’s previous state. To achieve the above, there are a number of different approaches: • Per-request execution: Every time dynamic content is needed, start a new program to process the request. • A pool of the requested processes or threads is already running. Each new request is handled by a separate process or thread. • Templating: We have already designed the page. Its request-specific contents are added and it is sent back to the user. • Web server extensions: The web server itself is extended through proprietary APIs to handle dynamic content. The third approach implies that the previous two produce themselves the HTML code for every request. Also, the third technique requires the presence of either the second (usually) or the first (seldom). The technologies that work for today’s web sites, according to the previous classifi- cation, are the following: • Per-request execution: Common Gateway Interface (CGI). • Fast CGI, Java Servlets.
    [Show full text]
  • 1 Historical Overview 2 Frontend Technologies
    1 Historical Overview Web Applications • http://www.evolutionoftheweb.com/ • + Mozilla 2 Frontend Technologies 2.1 Java World Servlet API • Fast API, faster than CGI used at the time (later FastCGI) • (HTTP-specific) classes for request/response processing • Response written directly into output stream sent to the client • Processes requests concurrently, Servlet 3.0 with asynchronous calls • Still used for non-HTML content (images, graphs, PDF) public class ServletDemo extends HttpServlet{ public void doGet(HttpServletRequest request, HttpServletResponse response) throws IOException{ PrintWriter out = response.getWriter(); out.println("<html>"); out.println("<body>"); out.println("<h1>Hello World!</h1>"); out.println("</body>"); out.println("</html>"); } } Java Server Pages • HTML or XML markup with pieces of Java code • JSPs are compiled into Servlets, e.g. as fast as Servlets • JSP Standard Tag Library (JSTL) - a library of common functionalities { e.g. forEach, if, out • Combobox updating is a nightmare :-) 1 Figure 1: JSP processing. From http://www.onjava.com/2002/08/28/ graphics/Jsp2_0303.gif JSP Example <html> <head> <title>JSP Example</title> </head> <body> <h3>Choose a hero:</h3> <form method="get"> <input type="checkbox" name="hero" value="Master Chief">Master Chief <input type="checkbox" name="hero" value="Cortana">Cortana <input type="checkbox" name="hero" value="Thomas Lasky">Thomas Lasky <input type="submit" value="Query"> </form> <% String[] heroes = request.getParameterValues("hero"); if (heroes != null) f %> <h3>You have
    [Show full text]