DOCSLIB.ORG

Documentation Release 0.9

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

www.wsgi.org Documentation Release 0.9 Feb 25, 2020 Contents 1 Contents 1 2 Contributing 43 3 Indices and tables 45 Bibliography 47 Index 49 i ii CHAPTER 1 Contents 1.1 What is WSGI? WSGI is the Web Server Gateway Interface. It is a specification that describes how a web server communicates with web applications, and how web applications can be chained together to process one request. WSGI is a Python standard described in detail in PEP 3333. For more, see Learn about WSGI. 1.2 Learn about WSGI • WSGI Tutorial by Clodoaldo Neto • WSGI Explorations in Python by Mike Orr • An Introduction to the Python Web Server Gateway Interface (WSGI) by Titus Brown • A Do-It-Yourself Framework by Ian Bicking • URL Parsing with WSGI by Ian Bicking • WSGI and WSGI Middleware is Easy by Ben Bangert • WSGI - Gateway or Glue by Mark Rees (particularly good as a starting point) • Mix and match Web components with Python WSGI by Uche Ogbuji • ‘Hello World with WSGI’ and WSGI Middleware by Rufus Pollock • Getting started with WSGI by Armin Ronacher • Why so many Python web frameworks? by Joe Gregorio (outlines the creation of a web framework using several WSGI-based tools) • Introducing WSGI: Python’s Secret Web Weapon by James Gardner [xml2006-09] • Introducing WSGI: Python’s Secret Web Weapon, Part Two by James Gardner [xml2006-10] 1 www.wsgi.org Documentation, Release 0.9 • test.wsgi a WSGI test app showing whether your WSGI environment is working (and also outputs some interest- ing informations like Python version, sys.path, WSGI environment, etc.). It can be directly used for mod_wsgi and easily for all other WSGI servers. When started directly from command line, it tries to use wsgiref’s simple server to serve the application. 1.3 Frameworks that run on WSGI This is an alphabetic list of frameworks known to support WSGI. The level and nature of their support sometimes varies, as do the APIs they provide. The descriptions here focus on that, and not the flavor of the frameworks them- selves. If you want to know more, follow the links! Note: Some frameworks really only support using pluggable WSGI servers, which means you get a number of options from HTTP, FastCGI, SCGI, threaded, forking, etc. However, not all such frameworks live well alongside other frameworks in the same process, or may require extra configuration. This is what is meant by noting when a framework supports WSGI servers, vs. a framework that supports a greater number of WSGI compositions, especially the kind of things noted in Middleware and libraries for WSGI Please feel free to expand on the list, the descriptions, or to make corrections. appier Appier is an object-oriented Python web framework built for super fast app development. It’s as lightweight as possible, but not too lightweight. It gives you the power of bigger frameworks, without their complexity. bobo Bobo is a light-weight framework. Its goal is to be easy to use and remember. Bottle Bottle is a fast and simple micro-framework for small web-applications. It offers request dispatching (Routes) with url parameter support, Templates, key/value Databases, a build-in HTTP Server and adapters for many third party WSGI/HTTP-server and template engines. All in a single file and with no dependencies other than the Python Standard Library. CherryPy CherryPy is a pythonic, object-oriented web development framework. Includes support for WSGI servers. CherryPy 3 includes better support for living alongside other WSGI frameworks, applications, and middleware. Django Includes support for WSGI servers Falcon Falcon is a high-performance Python framework for building cloud APIs. It encourages the REST architec- tural style, and tries to do as little as possible while remaining highly effective. Flask Flask is a microframework for Python based on Werkzeug, Jinja 2 and good intentions. It inherits its high WSGI usage and compliance from Werkzeug. notmm The notmm toolkit is a fork of Django that doesn’t get in your way. Features includes improved WSGI support (Paste), SQLAlchemy, and very few developers! ;-) PoorWSGI Poor WSGI for Python is light WGI connector with uri routing between WSGI server and your applica- tion. It have mod_python compatible request object, which is post to all uri or http state handler. Pycnic Pycnic is a mimimalist JSON API oriented framework for Python 2.7 and 3.x. It provides routing, cookies, and JSON error handling, while maintaining a small codebase. Pyramid Merger of the Pylons and repoze.bfg projects, Pyramid is a minimalist web framework aiming at compos- ability and making developers paying only for what they use. QWeb Another WSGI framework (not sure what the distinguishing features are) repoze.zope2 A module that implements an analogue of the Zope 2 ZPublisher, with some major simplifications and cleanups. Its core mission is to allow publishing existing Zope2 applications in a WSGI environment that externalizes some of the features of “classic” Zope2 into middleware. 2 Chapter 1. Contents www.wsgi.org Documentation, Release 0.9 TurboGears Database-driven app in minutes; inherits its WSGI support from CherryPy. web.py Makes web apps. A small RESTful library. web2py A full stack framework includes its own Database Abstraction Layer (with support for SQLite, MySQL, PostgreSQL, MSSQL, DB2, Informix, Oracle, FireBase, Ingres and Google App Engine), its own template laguage, and a web based IDE. web2py itself is a WSGI app. Not related to web.py. WebCore A nanoframework (only a few hundred lines of code) offering an entry_points-based dependency graph- ing extension system, MVC separation, reusable namespaces, and universal URL dispatch protocol with tight WebOb integration and natural Python semantics. weblayer weblayer is a lightweight, componentised package for writing WSGI applications. Zope 3 The venerable Python web framework, recreated anew in Zope 3, and now a WSGI application. It seems to have some WSGI bits deep inside the publisher, but they aren’t really documented at this time. 1.3.1 Deprecated Systems These systems still exist but got replaced by others or are unmaintained. Clever Harold Clever Harold is an ambitious web framework. It has many features for rapid, reusable, and reliable web application construction. Clever Harold is a complete WSGI framework. To build an application, you pick and choose the servers and components that fit your needs. Colubrid Colubrid is a WSGI publisher which simplifies python web developement. Colubrid is not a framework :-) Although some people like the idea of having found a framework in colubrid. All colubrid does for you is parsing form data / url parameters / cookies and providing a url dispatcher. Colubrid was replaced by Werkzeug. Nettri Nettri is a newcomer of Python World. It is under heavy development. Features includes CMS, Own template Engine, modules and more coming. Paste WebKit An implementation of the Webware servlet API using Paste infrastructure and WSGI. pycoon Pythonic web development framework based on XML pipelines and WSGI Pylons Full-stack Python web development framework combining the very best from the worlds of Ruby, Python and Perl. Pylons has been superseded by pyramid. repoze.bfg A Python WSGI-compliant web framework inspired by Zope, Pylons, and Django with built-in security and templating. repoze.bfg was renamed pyramid and moved under the Pylons project. RhubarbTart A pure-WSGI dispatcher and simple framework, inspired by CherryPy. simpleweb A simple Python WSGI-compliant web framework inspired by Django, TurboGears, and web.py. skunk.web A totally WSGI-ified version of SkunkWeb. Wareweb A rethinking of the Webware/WebKit servlet model, in a pure-WSGI framework. Not used widely. WebStack WebStack is a package which provides a simple, common API for Python Web applications, allowing such applications to run within many different environments with virtually no changes to application code. 1.4 Servers which support WSGI This is an alphabetic list of WSGI servers. In some cases these are WSGI-only systems, in other cases a package includes a server. 1.4. Servers which support WSGI 3 www.wsgi.org Documentation, Release 0.9 Please feel free to expand the list or descriptions. Direct links to documentation on how to use the server is especially appreciated. ajp-wsgi A threaded/forking WSGI server implemented in C (it embeds a Python interpreter to run the actual application). It communicates with the web server via AJP, and is known to work with mod_jk and mod_proxy_ajp. Also available in an SCGI flavor. Aspen A pure-Python web server (using the CherryPy module mentioned next) with three hooks to hang your WSGI on. cherrypy.wsgiserver CherryPy’s “high-speed, production ready, thread pooled, generic WSGI server.” Includes SSL support. Supports Transfer-Encoding: chunked. For details on running foreign (non-CherryPy) applications under the CherryPy WSGI server, see WSGI Support. See also the CherryPy wiki ModWSGI page. chiral.web.httpd A fast HTTP server supporting WSGI, with extensions for Coroutine-based pages with deeply-integrated COMET support. cogen.web.wsgi WSGI server with extensions for coroutine oriented programming. FAPWS Fapws is a WSGI binding between Python and libev. See also: author’s block, GoogleGroup. fcgiapp fcgiapp is a Python wrapper for the C FastCGI SDK. It’s used by PEAK’s FastCGI servers to provide WSGI-over-FastCGI. flup Includes threaded and forking versions of servers that support FastCGI, SCGI, and AJP protocols. gevent-fastcgi WSGI-over-FastCGI server implemented using gevent coroutine-based networking library. Supports FastCGI connection multiplexing. Includes adapters for Django and other frameworks that use Past- eDeploy. Gunicorn WSGI HTTP Server for UNIX, fast clients and nothing else. This is a port of Unicorn to Python and WSGI. ISAPI-WSGI An implementation of WSGI for running as a ISAPI extension under IIS.
Recommended publications
  • Interfacing Apache HTTP Server 2.4 with External Applications

    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).
  • Integrating Openshift Enterprise with Identity Management (Idm) in Red Hat Enterprise Linux

    Integrating Openshift Enterprise with Identity Management (Idm) in Red Hat Enterprise Linux

    Integrating OpenShift Enterprise with Identity Management (IdM) in Red Hat Enterprise Linux OpenShift Enterprise 2.2 IdM in Red Hat Enterprise Linux 7 Windows Server 2012 - Active Directory Integration Mark Heslin Principal Systems Engineer Version 1.1 January 2015 1801 Varsity Drive™ Raleigh NC 27606-2072 USA Phone: +1 919 754 3700 Phone: 888 733 4281 Fax: +1 919 754 3701 PO Box 13588 Research Triangle Park NC 27709 USA Linux is a registered trademark of Linus Torvalds. Red Hat, Red Hat Enterprise Linux and the Red Hat "Shadowman" logo are registered trademarks of Red Hat, Inc. in the United States and other countries. Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation. UNIX is a registered trademark of The Open Group. Intel, the Intel logo and Xeon are registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. All other trademarks referenced herein are the property of their respective owners. © 2014 by Red Hat, Inc. This material may be distributed only subject to the terms and conditions set forth in the Open Publication License, V1.0 or later (the latest version is presently available at http://www.opencontent.org/openpub/). The information contained herein is subject to change without notice. Red Hat, Inc. shall not be liable for technical or editorial errors or omissions contained herein. Distribution of modified versions of this document is prohibited without the explicit permission of Red Hat Inc. Distribution of this work or derivative of this work in any standard (paper) book form for commercial purposes is prohibited unless prior permission is obtained from Red Hat Inc.
  • Pylons Reference Documentation Release 1.0.2

    Pylons Reference Documentation Release 1.0.2

    Pylons Reference Documentation Release 1.0.2 Ben Bangert, Graham Higgins, James Gardner, Philip Jenvey January 12, 2018 Contents 1 Getting Started 1 1.1 Requirements...............................................1 1.2 Installing.................................................1 1.3 Creating a Pylons Project........................................3 1.4 Running the application.........................................4 1.5 Hello World...............................................4 2 Concepts of Pylons 7 2.1 The ‘Why’ of a Pylons Project......................................7 2.2 WSGI Applications...........................................8 2.3 WSGI Middleware............................................8 2.4 Controller Dispatch........................................... 10 2.5 Paster................................................... 10 2.6 Loading the Application......................................... 11 3 Controllers 13 3.1 Standard Controllers........................................... 14 3.2 Using the WSGI Controller to provide a WSGI service......................... 16 3.3 Using the REST Controller with a RESTful API............................ 17 3.4 Using the XML-RPC Controller for XML-RPC requests........................ 20 4 Views 23 4.1 Templates................................................. 24 4.2 Passing Variables to Templates...................................... 24 4.3 Default Template Variables....................................... 25 4.4 Configuring Template Engines...................................... 26 4.5 Custom
  • Insight: Semantic Provenance and Analysis Platform for Multi-Center Neurology Healthcare Research

    Insight: Semantic Provenance and Analysis Platform for Multi-Center Neurology Healthcare Research

    INSIGHT: SEMANTIC PROVENANCE AND ANALYSIS PLATFORM FOR MULTI-CENTER NEUROLOGY HEALTHCARE RESEARCH by PRIYA RAMESH Submitted in partial fulfillment of the requirements for the degree of MASTER OF SCIENCE Department of Electrical Engineering and Computer Science CASE WESTERN RESERVE UNIVERSITY January, 2016 ii CASE WESTERN RESERVE UNIVERSITY SCHOOL OF GRADUATE STUDIES We hereby approve the thesis of PRIYA RAMESH candidate for the Master of Science degree*. (signed) Dr. Satya S. Sahoo, Ph.D. (Chair of the committee) Dr. Kenneth A. Loparo, Ph.D. Dr. Martha Sajatovic, MD. (date) November 5th, 2015 *We also certify that written approval has been obtained for any proprietary material contained therein. iii Copyright © Priya Ramesh January, 2016 All rights reserved. iv TABLE OF CONTENTS TABLE OF CONTENTS iv LIST OF FIGURES vi LIST OF TABLES vii ACKNOWLEDGEMENT viii CHAPTER 1. INTRODUCTION 10 CHAPTER 2. BACKGROUND 13 2.1 Managing Epilepsy Well Network 13 2.1.1 Introduction 13 2.1.2 MEW database workgroup 16 2.1.3 MEW Network survey results 17 2.1.4 A common terminology for epilepsy self-management 19 2.1.5 Standardization of data elements 20 2.1.6 Data curation workflow for MEW Network datasets 21 2.1.7 MEW Network database design and functionality 26 2.2 Research Studies 27 CHAPTER 3. METHODS 30 3.1. Semantic Integration Module using MEW Common Data Elements (CDEs) 33 3.2. Data Exploration and Query Module 34 3.3. Ontology-based Inference Module 36 CHAPTER 4. INSIGHT SOFTWARE DEVELOPMENT 38 4.1 Objective 38 4.2 Agile Methodology 39 4.3 User Interface Development 41 CHAPTER 5.
  • Vasili Korol

    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.
  • Configuration Management at the Los Alamos National Laboratory

    Configuration Management at the Los Alamos National Laboratory

    Mac Configuration Management at the Los Alamos National Laboratory By Allan Marcus April, 2010 Overview.....................................................................................................................................1 The Challenge ...........................................................................................................................2 Product Selection.....................................................................................................................3 Getting Started..........................................................................................................................7 Basic Implementation............................................................................................................8 Configuration Management .............................................................................................. 14 Advanced Implementation................................................................................................ 16 How LANL uses Puppet ....................................................................................................... 20 Lessons Learned ................................................................................................................... 24 About the Author .................................................................................................................. 29 Appendix 1: puppet.sh........................................................................................................ 30 Appendix
  • Version Control Graphical Interface for Open Ondemand

    Version Control Graphical Interface for Open Ondemand

    VERSION CONTROL GRAPHICAL INTERFACE FOR OPEN ONDEMAND by HUAN CHEN Submitted in partial fulfillment of the requirements for the degree of Master of Science Department of Electrical Engineering and Computer Science CASE WESTERN RESERVE UNIVERSITY AUGUST 2018 CASE WESTERN RESERVE UNIVERSITY SCHOOL OF GRADUATE STUDIES We hereby approve the thesis/dissertation of Huan Chen candidate for the degree of Master of Science Committee Chair Chris Fietkiewicz Committee Member Christian Zorman Committee Member Roger Bielefeld Date of Defense June 27, 2018 TABLE OF CONTENTS Abstract CHAPTER 1: INTRODUCTION ............................................................................ 1 CHAPTER 2: METHODS ...................................................................................... 4 2.1 Installation for Environments and Open OnDemand .............................................. 4 2.1.1 Install SLURM ................................................................................................. 4 2.1.1.1 Create User .................................................................................... 4 2.1.1.2 Install and Configure Munge ........................................................... 5 2.1.1.3 Install and Configure SLURM ......................................................... 6 2.1.1.4 Enable Accounting ......................................................................... 7 2.1.2 Install Open OnDemand .................................................................................. 9 2.2 Git Version Control for Open OnDemand
  • Websocket Notifier

    Websocket Notifier

    Università degli Studi di Padova Dipartimento di Matematica Corso di Laurea in Informatica WebSocket Notifier: una RubyGem basata su WebSocket Tesi di laurea triennale Relatore Prof. Tullio Vardanega Laureando Federico Gobbo Anno Accademico 2015–2016 Federico Gobbo: WebSocket Notifier: una RubyGem basata su WebSocket, Tesi di laurea triennale, c Oct 2016. Sommario Il presente documento rappresenta la relazione finale dell’esperienza di stage condotta nell’azienda Si14 Spa. Esso è organizzato in quattro capitoli: 1. Descrizione dell’azienda: le origini, la natura, il mercato, i processi aziendali; 2. Le motivazioni alla base dell’esperienza di stage: i punti di vista dei portatori di interesse, ovvero l’azienda, l’università e il sottoscritto; 3. Presentazione del progetto di stage: processi e prodotti; 4. Valutazione retrospettiva sull’esperienza di stage. Convenzioni tipografiche Nel testo vengono utilizzate delle convenzioni tipografiche col seguente significato: • Corsivo: termine in lingua inglese; • Grassetto: termine rilevante; • Verbatim: nomi di file, codice; • Glossariojgj: termine presente nel glossario; • Riferimento1: termine associato a un riferimento bibliografico. iii “Make the best of the situation” — Eric Clapton Ringraziamenti Vorrei ringraziare il Prof. Tullio Vardanega, relatore della mia tesi, per l’aiuto, i buoni consigli e la disponibilità che ha dimostrato nei miei confronti. Ringrazio la mia famiglia, la mia ragazza e i miei amici per avermi permesso, col loro sostegno, di raggiungere questo traguardo. Padova, Oct 2016 Federico Gobbo v Indice 1 L’azienda: Si141 1.1 Storia . .1 1.2 Contesto aziendale . .1 1.2.1 I vantaggi dell’ecosistema M31 . .2 1.2.2 Tecnologia e innovazione . .2 1.2.3 Spin-off aziendali .
  • The Pyramid Web Application Development Framework Version 1.1

    The Pyramid Web Application Development Framework Version 1.1

    The Pyramid Web Application Development Framework Version 1.1 Chris McDonough CONTENTS Front Matteri Copyright, Trademarks, and Attributions iii Attributions............................................ iv Print Production.......................................... iv Contacting The Publisher..................................... iv HTML Version and Source Code................................. iv Typographical Conventionsv Author Introduction vii Audience............................................. vii Book Content........................................... viii The Genesis of repoze.bfg .................................. viii The Genesis of Pyramid...................................... ix Thanks............................................... ix I Narrative Documentation1 1 Pyramid Introduction3 1.1 What Is The Pylons Project?................................4 1.2 Pyramid and Other Web Frameworks............................4 2 Installing Pyramid7 2.1 Before You Install......................................7 2.1.1 If You Don’t Yet Have A Python Interpreter (UNIX)...............7 2.1.2 If You Don’t Yet Have A Python Interpreter (Windows)..............9 2.2 Installing Pyramid on a UNIX System...........................9 2.2.1 Installing the virtualenv Package....................... 10 2.2.2 Creating the Virtual Python Environment..................... 10 2.2.3 Installing Pyramid Into the Virtual Python Environment............. 11 2.3 Installing Pyramid on a Windows System......................... 11 2.4 Installing Pyramid on Google App Engine........................
  • Le Web Social Table Des Matières

    Le Web Social Table Des Matières

    Le Web Social Table des matières 1 Web social 1 1.1 Historique ............................................... 1 1.2 L'évolution du web social ....................................... 1 1.2.1 Blogs et wiki ......................................... 1 1.2.2 L'art social .......................................... 2 1.2.3 Le crowdsourcing ...................................... 2 1.2.4 Le développement d'applications mobiles .......................... 2 1.2.5 Des projets de logiciels communautaires ........................... 2 1.3 Du web social à la vie réelle ..................................... 2 1.4 Bibliographie ............................................. 3 1.5 Notes et références .......................................... 3 1.6 Voir aussi ............................................... 3 2 Réseautage social 4 2.1 Histoire ................................................ 4 2.2 Applications .............................................. 4 2.3 Modèle économique ......................................... 5 2.3.1 Commerce des données ................................... 5 2.3.2 Vente d'espaces publicitaires ................................. 5 2.3.3 Cession des actifs ....................................... 5 2.4 Domaines d'application ........................................ 5 2.4.1 Réseaux internes versus réseaux externes ........................... 6 2.4.2 Services en ligne de réseautage professionnels ........................ 6 2.4.3 Réseaux sociaux d'amis de la vie réelle ............................ 6 2.4.4 Services en ligne d'ancien
  • Rails Connector for CMS Fiona Infopark CMS Fiona Rails Connector for CMS Fiona

    Rails Connector for CMS Fiona Infopark CMS Fiona Rails Connector for CMS Fiona

    Infopark CMS Fiona Rails Connector for CMS Fiona Infopark CMS Fiona Rails Connector for CMS Fiona While every precaution has been taken in the preparation of all our technical documents, we make no expressed or implied warranty of any kind and assume no responsibility for errors or omissions. No liability is assumed for incidental or consequential damages in connection with or arising out of the use of the information or programs contained herein. All trademarks and copyrights referred to in this document are the property of their respective owners. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form, or by any means, electronic, mechanical, photocopying, recording, or otherwise, without our prior consent. Contents 1 Concepts . 7 1.1 Moving to Rails? . 7 1.1.1 Editorial and Live System . 7 1.1.2 Editorial Content and Layout are Handled Equally . 7 1.1.3 The Classical Live System is heterogeneous . 8 1.1.4 Ruby on Rails is an Integrated Framework . 8 1.1.5 Moving to Ruby on Rails . 8 1.1.6 Frequently Asked Questions About Moving to Rails . 9 1.2 What Is Ruby on Rails? . 10 1.3 Functions of Infopark Rails Connector . 11 1.4 Usage Scenarios for the Rails Connector . 11 1.5 The Playland Demo Application . 12 1.6 The Layout of a Rails Application . 18 1.7 Deployment . 18 1.8 CMS Layouts as Extensible Page Types . 19 1.9 Dedicated Controllers for Specific CMS File Formats . 20 1.10 Using the Rails Application as a Preview Server .
  • The Jumpgate Definitive Guide

    The Jumpgate Definitive Guide

    THE JUMPGATE DEFINITIVE GUIDE Compiled by: Odiche Special Thanks to: NETDEVIL© NewDawn IkeProf RazorKiss Lady Dracoe SpaceDrake Zalty’s And all the Pilots I have forgotten to thank! FACTIONS Solrain: Medium-fast ships, heavy, fast-recharging shields. A little light on firepower, lots of flexibility in ship loadout because of a large number of MODx slots. (MODx are worth reading up on in JOSSH). All Solrain ships have buckets of cargo space... the Solrain Fighter-class ship, the Intensity can carry a full set of equipment in it's hold to re-equip a downed squadmate. The Solrain Bomber and Medium Fighter are top-of-the-line, and they have a good Light Transport as well. Solrain ships are fairly forgiving for a new pilot; the glut of Flashfire MODxes they can equip can ensure their survival in situations where any other ship would be gunned down before it could escape. Solrain ships often utilize hit and run techniques in combat to gain the maximum advantage from their fast-recharging shields. Solrain ships can generally re-equip to a fairly good degree from their home stations. Solrain are typically RPed (Roleplayed) as greedy, profiteering traders. Which they are. Assassins, Mercenaries, Pirates, Traders, or Factionalists. To piss off a Solrain pilot, call him a Smurf. Quantar: Usually have the fastest ships in a given class. They also have a medium load- out of MODx slots. Quantar ships rely on maneuvrability to evade incoming fire; the Quantar fighters, the Typhoon, is an ideal wolf-pack ship. Their speed can carry them out of most trouble; only scouts or an Intensity can really catch them up, and if you are a skilled pilot, you can evade and escape from those also.