DOCSLIB.ORG

Web Services April 19, 2005 Web Services April 19, 2005 15-213

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Web Services April 19, 2005 Web Services April 19, 2005 15-213 15-213 “The course that gives CMU its Zip!” WebWeb ServicesServices AprilApril 19,19, 20052005 Topics HTTP Serving static content Serving dynamic content Proxies Presented by Kun Gao class26.ppt HistoryHistory ofof thethe WebWeb 1945: Vannevar Bush, “As we may think”, Atlantic Monthly, July, 1945. Describes the idea of a distributed hypertext system. A “Memex” that mimics the “web of trails” in our minds. 1989: Tim Berners-Lee (CERN) writes internal proposal to develop a distributed hypertext system. Connects “a web of notes with links.” Intended to help CERN physicists in large projects share and manage information 1990: Sir Tim BL writes a graphical browser for NeXT machines, and first web server ‘httpd’ – 2 – 15-213, S’05 WebWeb HistoryHistory (cont)(cont) 1992 NCSA server released 26 WWW servers worldwide 1993 Marc Andreessen releases first version of NCSA Mosaic browser (killer app of the 90’s) Mosaic version released for (Windows, Mac, Unix). Web (port 80) traffic at 1% of NSFNET backbone traffic. Over 200 WWW servers worldwide. 1994 Andreessen and colleagues leave NCSA to form “Mosaic Communications Corp” (predecessor to Netscape). – 3 – 15-213, S’05 InternetInternet HostsHosts – 4 – 15-213, S’05 InternetInternet AddressesAddresses IBM 9.0.0.0 - 9.255.255.255 12.0.0.0 - AT&T 12.255.255.255 13.0.0.0 - Xerox 13.255.255.255 15.0.0.0 - Hewlett-Packard 15.255.255.255 16.0.0.0 - Digital Equipment Corporation 16.255.255.255 17.0.0.0 - Apple Computer 17.255.255.255 18.0.0.0 - Massachusetts Institute of Technology 18.255.255.255 19.0.0.0 - Ford Motor Company 19.255.255.255 – 5 – 15-213, S’05 WhereWhere isis thisthis traffictraffic going?going? 1. Yahoo.com ! 2. MSN.com 3. Google.com 4. Passport.net 5. eBay.com … 2543. www.cmu.edu (23% to www.cs.cmu.edu ) – 6 – 15-213, S’05 WebWeb TransactionTransaction Clients and servers communicate using the HyperText Transfer Protocol (HTTP) HTTP request Client and server Web Web establish TCP connection client server Client requests content (browser) Server responds with HTTP response requested content (content) Client and server close connection (usually) Current version is HTTP/1.1 RFC 2616, June, 1999. – 7 – 15-213, S’05 HTTPHTTP ProtocolProtocol GET / HTTP/1.1 Client: request line host: www.aol.com Client: required HTTP/1.1 HOST header Client: empty line terminates headers . HTTP/1.0 200 OK Server: response line MIME-Version: 1.0 Server: followed by five response headers Date: Mon, 08 Jan 2001 04:59:42 GMT Server: NaviServer/2.0 AOLserver/2.3.3 Content-Type: text/html Server: expect HTML in the response body Content-Length: 42092 Server: expect 42,092 bytes in the resp body Server: empty line (“ \r\n”) terminates hdrs <html> Server: first HTML line in response body ... Server: 766 lines of HTML not shown. </html> Server: last HTML line in response body Connection closed by foreign host. Server: closes connection unix> Client: closes connection and terminates – 8 – 15-213, S’05 WebWeb ContentContent Web servers return content to clients content: a sequence of bytes with an associated MIME (Multipurpose Internet Mail Extensions) type Example MIME types text/html HTML document text/plain Unformatted text application/postscript Postcript document image/gif Binary image encoded in GIF format image/jpeg Binary image encoded in JPEG format – 9 – 15-213, S’05 StaticStatic andand DynamicDynamic ContentContent The content returned in HTTP responses can be either static or dynamic . Static content: content stored in files and retrieved in response to an HTTP request Examples: HTML files, images, audio clips. Dynamic content: content produced on-the-fly in response to an HTTP request Example: content produced by a program executed by the server on behalf of the client. Bottom line: All Web content is associated with a file that is managed by the server. – 10 – 15-213, S’05 URLsURLs Each file managed by a server has a unique name called a URL (Universal Resource Locator) URLs for static content: http://www.cs.cmu.edu:80/index.html http://www.cs.cmu.edu/index.html http://www.cs.cmu.edu Identifies a file called index.html, managed by a Web server at www.cs.cmu.edu that is listening on port 80. URLs for dynamic content: http://www.cs.cmu.edu:8000/cgi-bin/adder?15000&213 Identifies an executable file called adder , managed by a Web server at www.cs.cmu.edu that is listening on port 8000, that should be called with two argument strings: 15000 and 213 . – 11 – 15-213, S’05 HowHow ClientsClients andand ServersServers UseUse URLsURLs Example URL: http://www.aol.com:80 /index.html Clients use prefix (http://www.aol.com:80 ) to infer: What kind of server to contact (Web server) Where the server is ( www.aol.com ) What port it is listening on (80) Servers use suffix (/index.html ) to: Determine if request is for static or dynamic content. No hard and fast rules for this. Convention: executables reside in cgi-bin directory Find file on file system. Initial “ /” in suffix denotes home directory for requested content. Minimal suffix is “ /”, which all servers expand to some default home page (e.g., index.html ). – 12 – 15-213, S’05 AnatomyAnatomy ofof anan HTTPHTTP TransactionTransaction unix> telnet www.aol.com 80 Client: open connection to server Trying 205.188.146.23... Telnet prints 3 lines to the terminal Connected to aol.com. Escape character is '^]'. GET / HTTP/1.1 Client: request line host: www.aol.com Client: required HTTP/1.1 HOST header Client: empty line terminates headers . HTTP/1.0 200 OK Server: response line MIME-Version: 1.0 Server: followed by five response headers Date: Mon, 08 Jan 2001 04:59:42 GMT Server: NaviServer/2.0 AOLserver/2.3.3 Content-Type: text/html Server: expect HTML in the response body Content-Length: 42092 Server: expect 42,092 bytes in the resp body Server: empty line (“ \r\n”) terminates hdrs <html> Server: first HTML line in response body ... Server: 766 lines of HTML not shown. </html> Server: last HTML line in response body Connection closed by foreign host. Server: closes connection unix> Client: closes connection and terminates – 13 – 15-213, S’05 HTTPHTTP TransactionTransaction Clients and servers communicate using the HyperText Transfer Protocol (HTTP) HTTP request Client and server Web Web establish TCP connection client server Client requests content (browser) Server responds with HTTP response requested content (content) Client and server close connection (usually) Current version is HTTP/1.1 RFC 2616, June, 1999. – 14 – 15-213, S’05 HTTPHTTP RequestsRequests HTTP request is a request line , followed by zero or more request headers Request line: <method> < uri > <version> <version> is HTTP version of request ( HTTP/1.0 or HTTP/1.1 ) <uri> is typically URL for proxies, URL suffix for servers. A URL is a type of URI (Uniform Resource Identifier) See http://www.ietf.org/rfc/rfc2396.txt <method> is either GET, POST, OPTIONS, HEAD, PUT, DELETE, or TRACE. – 15 – 15-213, S’05 HTTPHTTP RequestRequest LineLine HTTP methods: GET : Retrieve static or dynamic content Arguments for dynamic content are in URI Workhorse method (99% of requests) POST : Retrieve dynamic content Arguments for dynamic content are in the request body OPTIONS : Get server or file attributes HEAD : Like GET but no data in response body PUT : Write a file to the server! DELETE : Delete a file on the server! TRACE : Echo request in response body Useful for debugging. – 16 – 15-213, S’05 HTTPHTTP RequestRequest HeadersHeaders Request headers: <header name>: <header data > Provide additional information to the server. Major differences between HTTP/1.1 and HTTP/1.0 HTTP/1.0 uses a new connection for each transaction. HTTP/1.1 also supports persistent connections multiple transactions over the same connection Connection: Keep-Alive HTTP/1.1 requires HOST header Host: kittyhawk.cmcl.cs.cmu.edu HTTP/1.1 adds additional support for caching – 17 – 15-213, S’05 GETGET RequestRequest toto ApacheApache ServerServer FromFrom BrowserBrowser URI is just the suffix, not the entire URL GET /test.html HTTP/1.1 Accept: */* Accept-Language: en-us Accept-Encoding: gzip, deflate User-Agent: Mozilla/4.0 (compatible; MSIE 4.01; Windows 98) Host: euro.ecom.cmu.edu Connection: Keep-Alive CRLF (\r\n) – 18 – 15-213, S’05 HTTPHTTP ResponsesResponses HTTP response is a response line followed by zero or more response headers . Response line: <version> <status code> <status msg > <version> is HTTP version of the response. <status code> is numeric status. <status msg> is corresponding English text. 200 OK Request was handled without error 403 Forbidden Server lacks permission to access file 404 Not found Server couldn’t find the file. Response headers: <header name>: <header data> Provide additional information about response Content-Type: MIME type of content in response body. Content-Length: Length of content in response body. – 19 – 15-213, S’05 GETGET ResponseResponse FromFrom ApacheApache ServerServer HTTP/1.1 200 OK Date: Thu, 22 Jul 1999 04:02:15 GMT Server: Apache/1.3.3 Ben-SSL/1.28 (Unix) Last-Modified: Thu, 22 Jul 1999 03:33:21 GMT ETag: "48bb2-4f-37969101" Accept-Ranges: bytes Content-Length: 79 Keep-Alive: timeout=15, max=100 Connection: Keep-Alive Content-Type: text/html CRLF <html> <head><title>Test page</title></head> <body> <h1>Test page</h1> </html> – 20 – 15-213, S’05 WebWeb ProxyProxy 1). Client Request 2). Proxy Request Client Proxy Server 4). Proxy Response 3). Server Response Web Proxy Interposed between Client & Server Usually serves as Firewall Sample Proxy Produces log of communication between client &
Load more

Recommended publications
  • A Reference Architecture for Web Servers
    A Reference Architecture for Web Servers Ahmed E. Hassan and Richard C. Holt Software Architecture Group (SWAG) Dept. of Computer Science University of Waterloo Waterloo, Ontario N2L 3G1 CANADA +1 (519) 888-4567 x 4671 {aeehassa, holt}@plg.uwaterloo.ca ABSTRACT document increases with the size and the complexity of the software system. Recently, a number of tools have A reference software architecture for a domain defines been developed to decrease this cost by helping to ex- the fundamental components of the domain and the tract the architecture of a software system [7, 16, 20, relations between them. Research has shown the bene- 21]. Using these tools, reverse engineering researchers fits of having a reference architecture for product de- have developed semi-automated processes to extract the velopment, software reuse, and maintenance. Many product’s architecture from available artifacts such as mature domains, such as compilers and operating sys- the product's source code and any available documenta- tems, have well-known reference architectures. tion. In this paper, we present a process to derive a reference The reference architecture [4] for a domain is an archi- architecture for a domain. We used this process to de- tecture template for all the software systems in the do- rive a reference architecture for web servers, which is a main. It defines the fundamental components of the relatively new domain. The paper presents the map- domain and the relations between these components. ping of this reference architecture to the architectures of The architecture for a particular product is an instance three open source web servers: Apache (80KLOC), of the reference architecture.
    [Show full text]
  • Server: Apache
    Modern Trends in Network Fingerprinting SecTor [11.21.07] Jay Graver Ryan Poppa // Fingerprinting Topics Why, What, Who & How? Tools in action Why Tools Break Tools EOL New Approaches New Tool // Why Fingerprint? WhiteHat needs accurate identification of hosts in a PenTest report BlackHat reconnaissance SysAdmins track down and identify new services or hosts when they appear on their network // What is a Fingerprint? Looking at something common … 192.168.2.187:8004 192.168.2.187 [152] 48 54 54 50 2f 31 2e 31 20 32 30 30 20 4f 4b 0d HTTP/1.1 200 OK. 0a 43 6f 6e 6e 65 63 74 69 6f 6e 3a 20 63 6c 6f .Connection: clo 73 65 0d 0a 41 6c 6c 6f 77 3a 20 4f 50 54 49 4f se..Allow: OPTIO 4e 53 2c 20 47 45 54 2c 20 48 45 41 44 2c 20 50 NS, GET, HEAD, P 4f 53 54 0d 0a 43 6f 6e 74 65 6e 74 2d 4c 65 6e OST..Content‐Len 67 74 68 3a 20 30 0d 0a 44 61 74 65 3a 20 46 72 gth: 0..Date: Fr 69 2c 20 30 32 20 4e 6f 76 20 32 30 30 37 20 32 i, 02 Nov 2007 2 32 3a 32 35 3a 31 38 20 47 4d 54 0d 0a 53 65 72 2:25:18 GMT..Ser 76 65 72 3a 20 6c 69 67 68 74 74 70 64 2f 31 2e ver: lighttpd/1. 34 2e 31 35 0d 0a 0d 0a 4.15...
    [Show full text]
  • Next Generation Web Scanning Presentation
    Next generation web scanning New Zealand: A case study First presented at KIWICON III 2009 By Andrew Horton aka urbanadventurer NZ Web Recon Goal: To scan all of New Zealand's web-space to see what's there. Requirements: – Targets – Scanning – Analysis Sounds easy, right? urbanadventurer (Andrew Horton) www.morningstarsecurity.com Targets urbanadventurer (Andrew Horton) www.morningstarsecurity.com Targets What does 'NZ web-space' mean? It could mean: •Geographically within NZ regardless of the TLD •The .nz TLD hosted anywhere •All of the above For this scan it means, IPs geographically within NZ urbanadventurer (Andrew Horton) www.morningstarsecurity.com Finding Targets We need creative methods to find targets urbanadventurer (Andrew Horton) www.morningstarsecurity.com DNS Zone Transfer urbanadventurer (Andrew Horton) www.morningstarsecurity.com Find IP addresses on IRC and by resolving lots of NZ websites 58.*.*.* 60.*.*.* 65.*.*.* 91.*.*.* 110.*.*.* 111.*.*.* 113.*.*.* 114.*.*.* 115.*.*.* 116.*.*.* 117.*.*.* 118.*.*.* 119.*.*.* 120.*.*.* 121.*.*.* 122.*.*.* 123.*.*.* 124.*.*.* 125.*.*.* 130.*.*.* 131.*.*.* 132.*.*.* 138.*.*.* 139.*.*.* 143.*.*.* 144.*.*.* 146.*.*.* 150.*.*.* 153.*.*.* 156.*.*.* 161.*.*.* 162.*.*.* 163.*.*.* 165.*.*.* 166.*.*.* 167.*.*.* 192.*.*.* 198.*.*.* 202.*.*.* 203.*.*.* 210.*.*.* 218.*.*.* 219.*.*.* 222.*.*.* 729,580,500 IPs. More than we want to try. urbanadventurer (Andrew Horton) www.morningstarsecurity.com IP address blocks in the IANA IPv4 Address Space Registry Prefix Designation Date Whois Status [1] -----
    [Show full text]
  • Linuxvilag-21.Pdf 12131KB 44 2012-05-28 10:16:00
    Töprengõ Nyíltan vagy zártan? programok fejlesztése rendkívüli iramban gyorsul: gombamód szaporodnak a jobbnál jobb programok, rengeteg bõvítmény készül minden operációs rend- Aszerhez. Azt hiszem, mindezt a Linux és más nyílt forrású rendszerek térnyerésének köszönhetjük. A forráskód hozzáfér- hetõsége nagyon sok embert arra ösztönöz, hogy saját „gondo- latkísérleteiket” is közzétegyék benne, ezzel is javítva a prog- ram minõségét, és esetleg bõvítve a felhasználási területét. Egyes programokra sokan azt mondják, hogy „halvaszületet- tek”, a nyílt forrású világban azonban nem egyszer láthattuk, © Kiskapu Kft. Minden jog fenntartva hogyan is támad fel halottaiból, ha nem is azonos néven és azonos feladattal, de a forráskód szintjén mindenképpen hasz- nosan egy-egy ilyen projekt! Ha nincs a Linux, valószínûleg senki nem kezdett volna bele az OpenBeOS fejlesztésébe; a Linux sikerei ösztönzõen hatnak az emberekre, a BeOS-ra- jongók pedig nem tétlenkednek, úgy döntöttek, hogyha a ked- venc rendszerük fejlesztése megszûnik, készítenek maguknak egy nyílt forrásút. Gondoljunk csak bele, hol tartanánk ma a nyílt forráskód nélkül? A Microsoft operációs rendszerei teljes- séggel eluralkodtak volna kicsiny bolygónkon, mindenki az önzõ harácsoló programírási gyakorlatnak behódolva alkotna nap mint nap, és bizony kemény pénzeket kellene leszurkolni minden egyes programért. Azt hiszem, a Linux mindenki számára hatalmas nyereség. A mostani programozópalánták ebbe a szabad világba születnek, így számukra már természetes lesz a forráskódok megosztása (hacsak el nem szegõdnek a sötét oldalra). E szabadság egyik nagy kérdése és veszélye a töredezettség. Hogy mire is gondolok: Linux-változatból nagyon sok van, a http://linuxlinks.com adatai szerint a Linuxnak 285 változata létezik – ezek vagy egyedi területet fednek le, vagy „csak” egyszerû Linux-kiadások.
    [Show full text]
  • Learning Management System Technologies and Software Solutions for Online Teaching: Tools and Applications
    Learning Management System Technologies and Software Solutions for Online Teaching: Tools and Applications Yefim Kats Ellis University, USA & Rivier College, USA InformatIon scIence reference Hershey • New York Director of Editorial Content: Kristin Klinger Director of Book Publications: Julia Mosemann Acquisitions Editor: Lindsay Johnston Development Editor: Elizabeth Ardner Typesetter: Gregory Snader Production Editor: Jamie Snavely Cover Design: Lisa Tosheff Printed at: Yurchak Printing Inc. Published in the United States of America by Information Science Reference (an imprint of IGI Global) 701 E. Chocolate Avenue Hershey PA 17033 Tel: 717-533-8845 Fax: 717-533-8661 E-mail: [email protected] Web site: http://www.igi-global.com/reference Copyright © 2010 by IGI Global. All rights reserved. No part of this publication may be reproduced, stored or distributed in any form or by any means, electronic or mechanical, including photocopying, without written permission from the publisher. Product or company names used in this set are for identification purposes only. Inclusion of the names of the products or companies does not indicate a claim of ownership by IGI Global of the trademark or registered trademark. Library of Congress Cataloging-in-Publication Data Learning management system technologies and software solutions for online teaching : tools and applications / Yefim Kats, editor. p. cm. Includes bibliographical references and index. Summary: "This book gives a general coverage of learning management systems followed by a comparative analysis of the particular LMS products, review of technologies supporting different aspect of educational process, and, the best practices and methodologies for LMS-supported course delivery"--Provided by publisher. ISBN 978-1-61520-853-1 (hardcover) -- ISBN 978-1-61520-854-8 (ebook) 1.
    [Show full text]
  • Telecentro Comunitario Agroindustrial Piloto En El Municipio De Silvia
    TELECENTRO COMUNITARIO AGROINDUSTRIAL PILOTO EN EL MUNICIPIO DE SILVIA ANEXO G: PLATAFORMAS DE DESARROLLO OPENACS Y dotLRN Contrato 420/2003 Colciencias - Universidad del Cauca. UNIVERSIDAD DEL CAUCA FACULTAD DE INGENIERIA ELECTRONICA Y TELECOMUNICACIONES FACULTAD DE CIENCIAS AGROPECUARIAS GRUPO I+D NUEVAS TECNOLOGÍAS EN TELECOMUNICACIONES GNTT GRUPO DE INGENIERIA TELEMATICA GIT DEPARTAMENTO DE AGROINDUSTRIA POPAYAN, 2004 INTRODUCCIÓN Mediante la implementación del Telecentro Agroindustrial Piloto se busca generar capacidades locales, conocimiento y brindar desarrollo agroindustrial en las zonas rurales, lo que permitirá un mejoramiento en las condiciones de la región. El Telecentro tiene como finalidad fortalecer social y económicamente a la comunidad de Silvia, ampliando espacios de participación y adaptando nuevos medios de capacitación (local y virtual), acceso a servicios de información y de desarrollo de actividades productivas y de comercialización. Este informe de carácter técnico presenta las tecnologías potenciales que permitirán ofrecer el servicio de tele-capacitación y tele-comercio (vitrina de productos). Estos servicios serán soportados a través de las plataformas de código abierto OpenACS y dotLRN disponibles bajo licencia Licencia Publica General GNU (GPL, General Public License). OpenACS es una plataforma para aplicaciones web orientadas a comunidades virtuales, permite divulgar gran variedad de información, realizar foros sobre temas específicos, servicios de encuestas, galerías de imágenes y una serie de aplicaciones orientadas a la participación de comunidades en línea. DotLRN es una plataforma de tele-educación que incluye los módulos más usuales de este tipo de entornos de enseñanza/aprendizaje: gestión de ficheros, foros, calendario, asignación de tareas, etc. Además, ofrece funcionalidades de trabajo y creación de documentos en grupo.
    [Show full text]
  • User's Guide to Aolpress
    User’s Guide to AOLpress 2.0 Do-it-Yourself Publishing for the Web 1997 America Online, Inc. AOL20-040797 Information in this document is subject to change without notice. Both real and fictitious companies, names, addresses, and data are used in examples herein. No part of this document may be reproduced without express written permission of America Online, Inc. 1997 America Online, Inc. All rights reserved. America Online is a registered trademark and AOLpress, AOLserver, PrimeHost, AOL, the AOL triangle logo, My Place, Netizens, and WebCrawler are trademarks of America Online, Inc. GNN is a registered trademark, and Global Network Navigator, GNNpress, and GNNserver are trademarks of Global Network Navigator, Inc. MiniWeb, NaviLink, NaviPress, NaviServer, and NaviService are trademarks of NaviSoft, Inc. Illustra is a trademark of Illustra Information Technologies, Inc. All other brand or product names are trademarks or registered trademarks of their respective companies or organizations. Author: Yvonne DeGraw Cover Art and Illustrations: Amy Luwis Special Thanks To: Thomas Storm, Cathe Gordon, Angela Howard, George W. Williams, V, Dave Long, Dave Bourgeois, Joel Thames, Natalee Press-Schaefer, Robin Balston, Linda T. Dozier, Jeff Dozier, Doug McKee, and Jeff Rawlings. Quick Table of Contents Contents Part 1: Getting Started Welcome! 11 Chapter 1 Installing AOLpress 17 Chapter 2 Create a Web Page in 10 Easy Steps 21 Chapter 3 Browsing with AOLpress 33 Part 2: Creating Pages Chapter 4 Web Pages and What to Put in Them 45 Chapter 5 Creating
    [Show full text]
  • 공개sw 솔루션 목록(2015.6.30)
    OS/DBMS/WEB/WAS 공개SW 솔루션 목록(2015.6.30) 순번 분류 솔루션명 라이선스 기술지원 홈페이지 제품개요 1 DBMS C-JDBC LGPL community http://c-jdbc.ow2.org/ 데이터베이스 클러스터 2 DBMS DB4 오브젝트(db4o) GPL & dOCL prof/community http://www.db4o.com 객체지향 메모리 데이터베이스 엔진 GPL v2, GPL v3, 3 DBMS Drizzle community http://www.drizzle.org/ MySQL 6.0에서 파생된 RDBMS BSD 4 DBMS H2 EPL, MPL community http://www.h2database.com/ 자바기반 RDBMS HSQLDB 5 DBMS (Hyper Structured Query BSD community http://www.hsqldb.org 경량의 Java 기반 관계형 데이터베이스 Language Database) 데이터 웨어하우스, OLAP서버, BI 시스템 운용을 목적으 6 DBMS LucidDB GPL v2, LGPL v2 community http://luciddb.sourceforge.net 로 개발된 오픈소스 DBMS GPL v3, AGPL v3, 7 DBMS Neo4j community http://www.neo4j.org 그래프 데이터베이스 commercial AGPL v3, 8 DBMS VoltDB Proprietary prof/community http://voltdb.com/ 인메모리기반 RDBMS License 오픈소스 관계형 데이터베이스 관리 시스템. 9 DBMS 마리아DB(MariaDB) GPLv2, LGPL prof/community https://mariadb.org/ MySQL과 동일한 소스 코드를 기반 세계에서 가장 널리 사용되고 있는 대표적인 10 DBMS 마이에스큐엘(MySQL) GPL v2 prof/community http://www.mysql.com 관계형 데이터베이스 ※ prof : Professional Support(전문업체 기술지원) ※ community : Community Support(커뮤니티 기술지원) OS/DBMS/WEB/WAS 공개SW 솔루션 목록(2015.6.30) 순번 분류 솔루션명 라이선스 기술지원 홈페이지 제품개요 IBM에서 기증한 cloudscape 소스 기반으로 11 DBMS 아파치 더비(Apache Derby) Apache v2 community http://db.apache.org/derby/ 개발된 Java 기반의 관계형 데이터베이스 Berkeley 오라클 버클리 DB Database License http://www.oracle.com/kr/products/database/ 슬리피캣을 인수한 오라클에서 제공하는 12 DBMS prof/community (Oracle Berkeley DB) or berkeley-db/index.html 고성능 임베디드 데이터베이스 Sleepycat License GPL or Postgresql 데이터베이스의 기반으로 상용화된 13 DBMS 잉그레스(Ingres) prof/community
    [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]
  • Linux WWW HOWTO Linux WWW HOWTO
    Linux WWW HOWTO Linux WWW HOWTO Table of Contents Linux WWW HOWTO .....................................................................................................................................1 by Mr. Poet, poet@linuxports.com..........................................................................................................1 1.Introduction...........................................................................................................................................1 2.Setting up WWW client software (Antiquated)....................................................................................1 3.Lynx......................................................................................................................................................1 4.Emacs−W3............................................................................................................................................1 5.Netscape Navigator/Communicator......................................................................................................1 6.Setting up WWW server systems.........................................................................................................2 7.Apache..................................................................................................................................................2 8.Web Server Add−ons............................................................................................................................2 9.Intranet Section.....................................................................................................................................2
    [Show full text]
  • Fortiweb 4.0 MR4 CLI Reference, 1St Edition
    CLI Reference for FortiWeb™ 4.0 MR4 Courtney Schwartz Contributors: George Csaba Martijn Duijm Patricia Siertsema Idan Soen Shiji Li Hao Xu Shiqiang Xu Forrest Zhang Contents Introduction ............................................................................................24 Scope ............................................................................................................................. 24 Conventions .................................................................................................................. 25 IP addresses............................................................................................................. 25 Cautions, notes, & tips.............................................................................................. 25 Typographic conventions.......................................................................................... 25 Command syntax...................................................................................................... 26 What’s new .............................................................................................28 Documentation changes .............................................................................................. 32 Using the CLI ..........................................................................................34 Connecting to the CLI................................................................................................... 34 Connecting to the CLI using a local console............................................................
    [Show full text]
  • Webdav a Network Protocol for Remote Collaborative Authoring on the Web E
    WebDAV A network protocol for remote collaborative authoring on the Web E. James Whitehead, Jr.† & Yaron Y. Goland‡ †Dept. of Info. and Computer Science, U.C. Irvine, USA, [email protected] ‡Microsoft Corporation, Redmond, WA, USA, [email protected] Abstract. Collaborative authoring tools generate network effects, where each tool’s value depends not just on the tool itself, but on the number of other people who also have compatible tools. We hypothesize that the best way to generate network effects and to add collaborative authoring capability to existing tools is to focus on the network protocol. This paper explores a protocol-centric approach to collaborative authoring by examining the requirements and functionality of the WebDAV protocol. Key features of the protocol are non- connection-oriented concurrency control, providing an upward migration path for existing non-collaborative applications, support for remote manipulation of the namespace of documents, and simultaneous satisfaction of a wide range of functional requirements. Introduction Despite many compelling research examples of collaborative authoring, so far their impact on actual authoring practice has been limited. While BSCW (Bentley et al., 1997) and HYPER-G (Maurer, 1996) have developed communities of use, electronic mail remains the dominant technology used for collaborative authoring, mainly due to its ubiquity. In order to perform collaborative authoring, all collaborators need to use compatible authoring tools—typically all collaborators use the same tools, tailor- made to support collaboration. To collaborate using PREP (Neuwirth et al., 1994), all collaborators need to use PREP, likewise for GROVE (Ellis et al., 1989) and DUPLEX (Pacull et al., 1994).
    [Show full text]