DOCSLIB.ORG

United States Patent (19) 11 Patent Number: 5,961,601 Iyengar (45) Date of Patent: Oct

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
United States Patent (19) 11 Patent Number: 5,961,601 Iyengar (45) Date of Patent: Oct USOO5961601A United States Patent (19) 11 Patent Number: 5,961,601 Iyengar (45) Date of Patent: Oct. 5, 1999 54 PRESERVING STATE INFORMATION INA Bertrand Ibrahim, “World-wide algorithm animation”, CONTINUING CONVERSATION BETWEEN Computer Networks and ISDN Systems, Elsevier Science A CLIENT AND SERVER NETWORKED WIA B.V., pp. 255–265, (1994). A STATELESS PROTOCOL Alan Falconer Slater, “Extending W3 clients”, Computer Networks and ISDN Systems, Elsevier Science B.V., pp. 75 Inventor: Arun K. Iyengar, Yorktown Heights, 61–68, (1995). 73 Assignee: International Business Machines (List continued on next page.) Corporation, Armonk, N.Y. Primary Examiner Mark H. Rinehart Attorney, Agent, or Firm Kevin M. Jordan 21 Appl. No.: 08/660,633 57 ABSTRACT 22 Filed: Jun. 7, 1996 A method and System for preserving State in computers 51 Int. Cl. ........................... G06F 13/38; G06F 15/17 communicating over networks, such as the World Wide Web 52 U.S. Cl. .......................... 709/229; 709/228; 709/218; (WWW) using stateless protocols, e.g., HTTP State is 709/203 preserved in a conversation between a client requesting 58 Field of Search ......................... 395/200.32, 200.48, Services from a Served by performing the Service and 395/200.53, 200.59, 182.02, 182.03, 182.05; identifying all continuations (hyperlinks) in an output from 709/202, 218, 223, 229, 228, 203; 714/4, the Service; recursively embedding the State information in 5, 7 all identified continuations in the output Sent to the client. The State information may be embedded and communicated 56) References Cited by the server to the client. Alternatively, dynamically down U.S. PATENT DOCUMENTS loadable program code may be used to embed the State information at the client. Additional features enable the 5,218,695 6/1993 Novecket al.. filtering and/or addition of hyperlinks and data output from 5,623,656 4/1997 Lyons ................................. 395/200.49 5,668,943 9/1997 Attanasio et al. ................. 395/182.05 the Services according to predetermined criteria. State infor 5,701,451 12/1997 Rogers et al. ..................... 395/200.32 mation may be embedded by modifying an identified con 5,708,780 1/1998 Levergood et al. ............... 395/200.12 tinuation which is a request for an HTML file, to invoke a 5,710,918 1/1998 Lagarde et al. ... ... 395/200.32 CGI converter program with the identified continuation and 5,774,670 6/1998 Montulli ............................ 395/200.57 the State information passed as arguments. State information may also be embedded by modifying an identified continu FOREIGN PATENT DOCUMENTS ation which is an invocation to a CGI program with the 0604010 10/1993 European Pat. Off.. identified continuation and the State information passed as 0625750 11/1994 European Pat. Off.. arguments, and the embedding Step is performed by the CGI program. Alternatively, an identified continuation which is OTHER PUBLICATIONS an invocation of a CGI program may be modified to invoke “Haht Software Premiers HahtSite at Demo 96', PR News a CGI converter program with the identified continuation, an wire, Jan. 29, 1996. argument counter which indicates a number of arguments “Proposed HTTP State Management Mechanism”, Montulli asSociated with the CGI program, and the State information et al., HTTP Working Group, Feb. 16, 1996. passed as arguments. Here, the embedding is performed by Louis Perrochon et al., “IDLE: Unified W3-access to inter the converter program. active information servers', Computer Networks and ISDN Systems, Elsevier Science B.V., pp. 927–938, (1995). 68 Claims, 10 Drawing Sheets CLENT WEB BROWSER 450 CONNECTION MANAGER DATABASE (OPTIONAL) HTML FIES CGI PROGRAMS 5,961,601 Page 2 OTHER PUBLICATIONS “Hypertext Transfer Protocol-HTTP/1.0” http://www.ic “Behind The Scenes of The Adventure Web”, http://tww S.uci.edu/pub/ietf/http/draft-ietf-http-v10-spec-03.html, w.stanford.edu/adventure/impl.html Feb. 23, 1996. by T. Berners-Lee, R. Fielding, and H. Frystyk, Sep. 4, “Aug. 1995 Web Watch”, http:www.netgen.com/corpinfo/ 1995. press/webwtchv6n8.html Feb. 2, 1996. “Zebrafish Database', http://zfish.uoregon.edu/Zf info/ “Network News Transfer Protocol: A Proposed Standard for dbase/arch.html Oct. 24, 1995. the Stream-Based Transmission of News”, RFC 977, B. “Porting Interactive Applications to the Web”, http://ksi.cp Kantor and P. Lapsley, UC San Diego and UC Berkeley, Feb. sc.ucalgary.ca/articles/WWW/PortWeb/PortWeb.html Dec. 1986, http://ds.internic.net/rfc/rfc977.txt. 7, 1995. “MBA/MBARI Live Link to The Technology Museum of “Simple Mail Transfer Protocol", RFC 821, J.B. Postel, Innovation in San Jose' http://rockfish.mbari.org/BayLink/ Information Sciences http://ds.internic.net/std/std 10.txt. http prb.html Aug. 2, 1995. “Persistent Client State HTTP Cookies”, Netscape Commu J. Postel and J.K. Reynolds, “File Transfer Protocol (FTP)”, nications Corporation, 1996 http://home.netscape.com/ RFC 959, Information Sciences Institute, USC, Oct. 1985 newsref/std/cookie Spec.html. http://ds.internic.net/std/std9.txt. U.S. Patent Oct. 5, 1999 Sheet 1 of 10 5,961,601 T.J. Watson Research Center. Yorktown (left) and Hawthorne. O Welcome O Local Education Outreach O Visitor info and local site directions O Local hotels O IBM home page -- IBM Research home page G Click on icon to send your comments. Or, contact webmaster(awatson.ibm.com IBM home page Order Search Contact IBM | Help (C) (TM) FG. PRIOR ART U.S. Patent Oct. 5, 1999 Sheet 2 of 10 5,961,601 FG.2 PRIOR ART SKYLINE SUPPLIERS REGISTRATION FORM USERID PASSWORD PASSWORD (FOR VERIFICATION) ACTUAL NAME COMPANY E-MAIL ADDRESS PHONE NUMBER (RESET FORM) U.S. Patent Oct. 5, 1999 Sheet 3 of 10 5,961,601 FG.3 PRIOR ART 450 CLENT SERVER COMPLETED GENERATED FORM FORM INTERNET HIDDEN HIDDEN STATE STATE WARIABLES WARIABLES SERVER A.10 U.S. Patent Oct. 5, 1999 Sheet 4 of 10 5,961,601 FG.4 CLIENT SERVER CLIENT REQUESTS A SERVICE FROM THE SERVER STATELESS PROTOCOL CALL TO 505 YES 500 CONVERT 2. NO TO STEP 510 530 PRESERVATION 525 515 p. EXECUTE SERVICE YES CENT RECEIVES STATELESS PROTOCOL SEND TO CENT 520 SERVICE OUTPUT WITH CONTINUATIONS YCONVERT LOGIC MODIFIES AL CONTINUATIONS STATELESS PRODUCED BY THE SERVICE TO PROTOCOL EMBED STATE AND EXPLCT 540 CALL TO CONVERT 2' YES CONTINUATION SELECTED 530 CONVERT 2. INVOKES SERVICE WITH ARGUMENTS NO AND STATE WARIABLES END CONVERSATION 535 PASS OUTPUT AND STATE WARIABLES TO CONVERT 1 U.S. Patent Oct. 5, 1999 Sheet 5 of 10 5,961,601 ROUTING AND CONTROL INFO SERVICE 1 SERVICE ARGUMENTS FG.5 601 650 605 610 685 670 ROUTING AND STATE CONTROL INFO CONVERT 2 SERVICE 1 SERVICE ARGUMENTS WARIABLES 680 F.G. 6 U.S. Patent Oct. 5, 1999 Sheet 6 of 10 5,961,601 FG.7d SERVER 410 CLIENT CONVERTER - INTERNET OTHER BROWSER CG 414 PROGRAMS 460 413 HTML/CG DBMS 470 CONNECTION 475 MANAGER DATABASE 427 (OPTIONAL) 429 CGI PROGRAMS U.S. Patent Oct. 5, 1999 Sheet 7 of 10 5,961,601 FIG.7b CLIENT ACCESSES HOME PAGE 700 (STATELESS) CLENT BEGINS BROWSNG PRODUCT CATALOG 710 (STATELESS) CLIENT BROWSES NEW 720 CATALOG PAGE (STATELESS) CLIENT DESIRES TO 730 PURCHASE AN TEM (STATELESS) 740 CLIENT ENTERS USER-ID, PASSWORD 745 STATE WARIABLES EMBEDDED; USER-ID, SESSION-ID CLIENT BROWSES ADDITIONAL CATALOG PAGES (CONTINUATION SELECTED). 750 STATE WARIABLES PRESERVED FOR REMAINDER OF CONVERSATION U.S. Patent Oct. 5, 1999 Sheet 8 of 10 5,961,601 FG.8 INTERNET CLENT SERVER CLENT SELECTS HYPERLINK CGI PROGRAM BEGINS 810 PRESERVING STATE By 740' CALLING CONVERT 1 811 CONVERT 1 MODIFIES 81 3 LINKS TO HTML FILES CLIENT RECEIVES MODIFIED HTML TEXT Y CONVERT 17 MODIFIES LINKS TO CGI PROGRAMS CLIENT SELECTS HYPERTEXT LINK CALL TO Y CONVERT 2. ' PROCESS REQUEST FILE OR PROGRAM PASSED TO CONVERT 2. ' FETCH FILE AND PASS WITH STATE ARGS TOY CONVERT 1 7 EXECUTE PROGRAM & PASS OUTPUT WITH STATE ARGS TO 818 Y CONVERT 11 5,961,601 1 2 PRESERVING STATE INFORMATION IN A to use, separated from the rest of the locator by a “:”. Next CONTINUING CONVERSATION BETWEEN is the hostname or IP address of the target host; this is A CLIENT AND SERVER NETWORKED WIA delimited by the “//” on the left and on the right by a "/" or A STATELESS PROTOCOL optionally a “:”. The port number is optional, and is delim ited on the left from the hostname by a “:” and on the right FIELD OF THE INVENTION by a "/". The fourth component is the actual file name or program name. In this example, the ".html” extension means This invention is related to computers and computer that this is an HTML file. networks. In particular, the invention is related to computers Hyperlink (or Hypertext Link) preserving State while communicating over networkS via A network address embedded in a word, phrase, icon or StateleSS protocols. Even more particularly, the invention is picture that is activated when you Select it. Information related to a method and System for preserving State in about that item is returned to the client and displayed using computers communicating over the Internet, Specifically the a Web browser. World Wide Web, using the HyperText Transfer Protocol HyperText Markup Language (HTML) (HTTP). 15 HTML is the language used by Web servers to create and connect documents that are viewed by Web clients. HTML CROSS-REFERENCE TO RELATED PATENTS uses Hypertext documents. Other uses of Hypertext docu The present invention is related to the following United ments are described in U.S. Pat. No. 5,204,947, granted Apr. States of America Patents: 20, 1993 to Bernstein et al.; U.S. Pat. No.
Load more

Recommended publications
  • Lesson-13: INTERNET ENABLED SYSTEMS NETWORK PROTOCOLS
    DEVICES AND COMMUNICATION BUSES FOR DEVICES NETWORK– Lesson-13: INTERNET ENABLED SYSTEMS NETWORK PROTOCOLS Chapter-5 L13: "Embedded Systems - Architecture, Programming and Design", 2015 1 Raj Kamal, Publs.: McGraw-Hill Education Internet enabled embedded system Communication to other system on the Internet. Use html (hyper text markup language) or MIME (Multipurpose Internet Mail Extension) type files Use TCP (transport control protocol) or UDP (user datagram protocol) as transport layer protocol Chapter-5 L13: "Embedded Systems - Architecture, Programming and Design", 2015 2 Raj Kamal, Publs.: McGraw-Hill Education Internet enabled embedded system Addressed by an IP address Use IP (internet protocol) at network layer protocol Chapter-5 L13: "Embedded Systems - Architecture, Programming and Design", 2015 3 Raj Kamal, Publs.: McGraw-Hill Education MIME Format to enable attachment of multiple types of files txt (text file) doc (MSOFFICE Word document file) gif (graphic image format file) jpg (jpg format image file) wav format voice or music file Chapter-5 L13: "Embedded Systems - Architecture, Programming and Design", 2015 4 Raj Kamal, Publs.: McGraw-Hill Education A system at one IP address Communication with other system at another IP address using the physical connections on the Internet and routers Since Internet is global network, the system connects to remotely as well as short range located system. Chapter-5 L13: "Embedded Systems - Architecture, Programming and Design", 2015 5 Raj Kamal, Publs.: McGraw-Hill Education
    [Show full text]
  • Stateless Protocol in Java
    Stateless Protocol In Java Self-disliked Devin marcelling some Monaco after bardy Niki spittings malignly. Castled Ashish turpentined or unbuild some lorgnette obsessionally, however emergency Matthew phenomenize apostolically or stridulate. Is Francisco crustier or glyptic after subapostolic Scarface climaxes so delayingly? You will add it completely stands for keeping of code has not connect in building their subdirectories and protocol in different purposes only platform that subsequent requests to build a part of guaranteeing the workload Identify the grain of browser used to make an request. Your credit card details and path itself does this is something is not! But ads help us give step free had to Brainly. Modeling your complex computing system using CSP will result in splitting it raw in many smaller, stateless subsystems that communicate using channels. Can be stateless? Please enter right email to send this project is so. Trace was last two layers in there was, while stateless protocol that state they are amazing at maps between asp session id stored safely within them? Our mission is off create a smarter world by simplifying and accelerating the learning process. If you to analyse traffic over http protocol of interactions. Another server to uniquely and subscriptions, that machines could sort them? What is session tracking? All of java objects will check for otp grew out in java servlet section you write higher throughput with stateless protocol in java servlet to ensure premium tier caches. The ASG ensures that a node keeps running by comparing the shoulder state leaving the desired state. You sure to stateless protocols and hit enter your system scale by spring session and http is shopping cart, it work of a new.
    [Show full text]
  • Media Distribution Using Overlay Multicast and Peer-To-Peer Technologies
    Media Distribution using Overlay Multicast and Peer-to-Peer Technologies Dissertation zur Erlangung des Doktorgrades der Mathematisch-Naturwissenschaftlichen Fakultäten der Georg-August-Universität zu Göttingen vorgelegt von Jun Lei aus Huzhou, China Göttingen 2008 D7 Referent: Professor Dr. Xiaoming Fu. Korreferent: Professor Dr. Dieter Hogrefe Tag der mündlichen Prüfung: 17 Juli, 2008 Abstract The explosive growth of multimedia services and applications (e.g. media streaming) demands an efficient, deployable media distribution system on the Internet. Although native IP multicast is regarded as an efficient way of delivering media streams to a group of receivers, it faces a number of technical and operational issues which have eventually prevented its widespread usage. The aim of this work is therefore to build a scalable, efficient, reliable and incrementally deployable infrastructure for supporting media distribution services. In this thesis, a new framework named Dynamic Mesh-based overlay Multicast Protocol (DMMP) framework, and two important extensions to the basic DMMP protocol, namely Self-improved DMMP protocol (DMMP+) and Interest-shared Group Management (IGMT) protocol for DMMP, are developed to efficiently serve a large number of concurrent clients with relatively high inbound bandwidth and low start-up delay. The DMMP framework dynamically manages a two-tier hierarchy, i.e., an overlay core so-called dynamic mesh, and clusters without relying on classic IP multicast. The key idea is to let a number of end hosts get selected and self-organized into the overlay hierarchy, and dynamically maintain such a hierarchy. In comparison to prior application layer multicast protocols, DMMP is more adaptive to group size changes, and provides efficient and reliable media delivery with less control overhead and less packet loss.
    [Show full text]
  • A Stateless Network Stack for Improved Scalability, Resilience, and Flexibility
    Trickles: A Stateless Network Stack for Improved Scalability, Resilience, and Flexibility Alan Shieh Andrew C. Myers Emin Gun¨ Sirer Dept. of Computer Science Cornell University Ithaca, NY 14853 {ashieh,andru,egs}@cs.cornell.edu Abstract Consider a point-to-point connection between a web Traditional operating system interfaces and network pro- client and server. The system state consists of TCP proto- tocol implementations force system state to be kept on col parameters, such as window size, RTT estimate, and both sides of a connection. Such state ties the connec- slow-start threshold, as well as application-level data, tion to an endpoint, impedes transparent failover, per- such as user id, session id, and authentication status. mits denial-of-service attacks, and limits scalability. This There are only three locations where state can be stored, paper introduces a novel TCP-like transport protocol namely, the two endpoints and the network in the mid- and a new interface to replace sockets that together en- dle. While the end-to-end argument provides guidance able all state to be kept on one endpoint, allowing the on where not to place state and implement functionality, other endpoint, typically the server, to operate without it still leaves a considerable amount of design flexibility any per-connection state. Called Trickles, this approach that has remained largely unexplored. enables servers to scale well with increasing numbers Traditional systems based on sockets and TCP/IP dis- of clients, consume fewer resources, and better resist tribute session state across both sides of a point-to-point denial-of-service attacks.
    [Show full text]
  • Http Request Response.Pdf
    yet another insignificant programming notes... | HOME HTTP (HyperText Transfer Protocol) Basics Introduction The WEB Internet (or The Web) is a massive distributed client/server information system as depicted in the following diagram. Many applications are running concurrently over the Web, such as web browsing/surfing, e-mail, file transfer, audio & video streaming, and so on. In order for proper communication to take place between the client and the server, these applications must agree on a specific application-level protocol such as HTTP, FTP, SMTP, POP, and etc. open in browser PRO version Are you a developer? Try out the HTML to PDF API pdfcrowd.com HyperText Transfer Protocol (HTTP) HTTP (Hypertext Transfer Protocol) is perhaps the most popular application protocol used in the Internet (or The WEB). HTTP is an asymmetric request-response client-server protocol as illustrated. An HTTP client sends a request message to an HTTP server. The server, in turn, returns a response message. In other words, HTTP is a pull protocol, the client pulls information from the server (instead of server pushes information down to the client). HTTP is a stateless protocol. In other words, the current request does not know what has been done in the previous requests. HTTP permits negotiating of data type and representation, so as to allow systems to be built independently of the data being transferred. Quoting from the RFC2616: "The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. It is a generic, stateless, protocol which can be used for many tasks beyond its use for hypertext, such as name servers and distributed object management systems, through extension of its request methods, error codes and headers." Browser Whenever you issue a URL from your browser to get a web resource using HTTP, e.g.
    [Show full text]
  • The World Wide Web
    Bryn Mawr College Scholarship, Research, and Creative Work at Bryn Mawr College Computer Science Faculty Research and Computer Science Scholarship 1999 The orW ld Wide Web H. Berghel Doug Blank Bryn Mawr College, [email protected] Let us know how access to this document benefits ouy . Follow this and additional works at: http://repository.brynmawr.edu/compsci_pubs Part of the Computer Sciences Commons Custom Citation Berghel, H. and D. Blank. (1999). The orldW Wide Web, in M. Zelkowitz (ed.), Advances in Computing, v. 48, Academic Press, pp. 178-218. This paper is posted at Scholarship, Research, and Creative Work at Bryn Mawr College. http://repository.brynmawr.edu/compsci_pubs/22 For more information, please contact [email protected]. Berghel, H., and Blank, D. (1999) The World Wide Web. In Advances in Computing, M. Zelkowitz (Ed). Academic Press, NY. THE WORLD WIDE WEB Hal Berghel & Douglas Blank PREPRINT Department of Computer Science University of Arkansas ABSTRACT This article provides a high-level overview of the World Wide Web in the context of a wide range of other Internet information access and delivery services. This overview will include client-side, server-side and "user-side" perspectives. Underlying Web technologies as well as current technology extensions to the Web will also be covered. Social implications of Web technology will also be addressed. TABLE OF CONTENTS 1. INTRODUCTION 2. THE INTERNET INFRASTRUCTURE 3. THE SUCCESS OF THE WEB 4. PERSPECTIVES 4.1 END USERS' PERSPECTIVE 4.2 HISTORICAL PERSPECTIVE 5. THE UNDERLYING TECHNOLOGIES 5.1 HYPERTEXT MARKUP LANGUAGE (HTML) 5.2 HYPERTEXT TRANSFER PROTOCOL (HTTP) 6.
    [Show full text]
  • Development Tools
    Development Tools n today’s world, we see Web protocol, Hypertext Transfer Protocol (HTTP), simplifies WS even more. Statelessness Services (WS) in action and HTTP let us take advantage of many existing tools. The whole spectrum of I everywhere from online shopping Internet infrastructure helps us implement REST-based WS. From Java libraries that and shipping trackers to mapping provide valid HTTP sessions to caching web proxies, all of the infrastructure on the and geolocation tools. The methods Web works for us. used to create WS are just as broad and varied as the tools that use WS. What exactly is a stateless protocol? Imagine a stateless bank teller. A conversation However, some of the protocols defined might go something like this: by the WS- documents seem to exist only for Oracle to sell consulting Jason: “Excuse me, ma’am, what is my balance?” contracts. One can easily drown in the Teller: “I’m sorry, sir, for what account?” alphabet soup of UDDI, WSDL, and Jason: “Of course. What is the balance of account 1234?” SOAP. Learning SOAP (Simple Object Teller: “I’m sorry, who is the account holder for account 1234?” Access Protocol) reveals there is nothing simple about it. Add to that the fact that Jason: “What is the balance of account 1234 held by Jason?” Java and .net are incompatible in subtle Teller: “I’m sorry, what is the password for account 1234 held by Jason?” ways, which creates extra complexity. Jason: “What is the balance of account 1234 held by Jason with password GetItAlready” REpresentational State Transfer (REST) Teller: “The balance is 37 cents.” eliminates much of the formality imposed by a WSDL-style WS.
    [Show full text]
  • Stateful Anycast for Ddos Mitigation
    Stateful Anycast for DDoS Mitigation by Richard E. Hansen S.B. Electrical Engineering and Computer Science Massachusetts Institute of Technology, 2006 Submitted to the Department of Electrical Engineering and Computer Science in partial fulfillment of the requirements for the degree of Master of Engineering in Electrical Engineering and Computer Science at the Massachusetts Institute of Technology June 2007 © 2007 Massachusetts Institute of Technology. All rights reserved. Author............................................................................... Department of Electrical Engineering and Computer Science May 28, 2007 Certified by.......................................................................... Karen R. Sollins Principal Research Scientist Thesis Supervisor Accepted by......................................................................... Arthur C. Smith Professor of Electrical Engineering Chairman, Department Committee on Graduate Theses 2 Stateful Anycast for DDoS Mitigation by Richard E. Hansen Submitted to the Department of Electrical Engineering and Computer Science on May 28, 2007 in partial fulfillment of the requirements for the degree of Master of Engineering in Electrical Engineering and Computer Science Abstract Distributed denial-of-service (DDoS) attacks can easily cripple victim hosts or networks, yet effective defenses remain elusive. Normal anycast can be used to force the diffusion of attack traffic over a group of several hosts to increase the difficulty of saturating resources at or near any one of the hosts. However, because a packet sent to the anycast group may be delivered to any member, anycast does not support protocols that require a group member to maintain state (such as TCP). This makes anycast impractical for most applications of interest. This document describes the design of Stateful Anycast, a conceptual anycast-like network service based on IP anycast. Stateful Anycast is designed to support state- ful sessions without losing anycast’s ability to defend against DDoS attacks.
    [Show full text]
  • HTTP Overview
    HHTTTTPP -- OOVVEERRVVIIEEWW http://www.tutorialspoint.com/http/http_overview.htm Copyright © tutorialspoint.com The Hypertext Transfer Protocol HTTP is an application-level protocol for distributed, collaborative, hypermedia information systems. This is the foundation for data communication for the World Wide Web i. e. internet since 1990. HTTP is a generic and stateless protocol which can be used for other purposes as well using extensions of its request methods, error codes, and headers. Basically, HTTP is a TCP/IP based communication protocol, that is used to deliver data HTMLfiles, imagefiles, queryresults, etc. on the World Wide Web. The default port is TCP 80, but other ports can be used as well. It provides a standardized way for computers to communicate with each other. HTTP specification specifies how clients' request data will be constructed and sent to the server, and how the servers respond to these requests. Basic Features There are three basic features that make HTTP a simple but powerful protocol: HTTP is connectionless: The HTTP client, i.e., a browser initiates an HTTP request and after a request is made, the client disconnects from the server and waits for a response. The server processes the request and re-establishes the connection with the client to send a response back. HTTP is media independent: It means, any type of data can be sent by HTTP as long as both the client and the server know how to handle the data content. It is required for the client as well as the server to specify the content type using appropriate MIME-type. HTTP is stateless: As mentioned above, HTTP is connectionless and it is a direct result of HTTP being a stateless protocol.
    [Show full text]
  • Transfer Protocols for Digital Media Workflows Contents 2 Introduction
    Transfer Protocols for Digital Media Workflows Contents 2 Introduction Introduction to Protocols Introduction to Protocols 2 1 User Datagram Protocol (UDP) 3 With the many advances that have been made in digital media file formats, compression, and distribution – the RUDP 6 technology for the transfer of rich media has remained relatively unchanged for over 40 years. UDPS 6 New lightweight codecs and file choices are regularly introduced to provide content viewing and a downloadable proxy for production. However, with a growing influx of content makers looking to maintain the value of a File Transfer Protocol (FTP) 6 2 large, complex master file for productions, the need to transfer, share and move these large files has various FTPS 8 challenges in speed, bandwidth and security. SFTP 8 Here we take a look at some of the transfer building blocks commonly used throughout the video industry. For the purpose of this document we are going to focus on the three main protocols in practice today – UDP, Hypertext Transfer Protocol (HTTP) 9 3 FTP and HTTP. HTTP 1.1 11 4 Key Considerations 12 11 Transfer Speed Times 13 The Future 14 5 About Aframe 15 Share this... Transfer Protocols for Digital Media Workflows Transfer Protocols for Digital Media Workflows 1 UDP User Datagram Protocol 4 UDP User Datagram Protocol (UDP) Essentials • Typically used for streaming media assets over IP. • UDP will optimize your transfer rates for large data sets when there is high latency or packet loss over the network. Background Developed and released by David P Reed in 1980, thanks to its fast transfer rates and capability of handling large files, UDP is quite often the method to be leveraged for video conferencing and video streaming needs.
    [Show full text]
  • Measurement and Analysis of HTTP Traffic
    Journal of Network and Systems Management (c 2005) DOI: 10.1007/s10922-005-9000-y Thresholds Edited by Lawrence Bernstein Measurement and Analysis of HTTP Traffic Yogesh Bhole1,2 and Adrian Popescu1 The usage of Internet is rapidly increasing and a large part of the Internet traffic is generated by the World Wide Web (WWW) and the associated protocol HyperText Transfer Protocol (HTTP). Several important parameters that affect the performance of the WWW are bandwidth, scalability, and latency. To tackle these parameters and to improve the overall performance of the system, it is important to understand and to characterize the application level characteristics. This article is reporting on the mea- surement and analysis of HTTP traffic collected on the student access network at the Blekinge Institute of Technology in Karlskrona, Sweden. The analysis is done on var- ious HTTP traffic parameters, e.g., inter-session timings, inter-arrival timings, request message sizes, response code, and number of transactions. The reported results can be useful for building synthetic workloads for simulation and benchmarking purposes. KEY WORDS: World Wide Web; HyperText Transfer Protocol; performance; service level agreement . 1. INTRODUCTION The work on World Wide Web (WWW) started in 1989 with the development of a set of simple protocols and formats [1]. WWW has afterwards been more and FO more developed and also used as a test bed for sophisticated concepts for hyper- media and information retrieval. The consequence has been that WWW has had a major impact on modern life and influenced our lives in many ways. It has, for instance, become the preferred way of content distribution.
    [Show full text]
  • Hypertext Transfer Protocol -- HTTP/1.1
    Network Working Group R. Fielding Request for Comments: 2616 UC Irvine Obsoletes: 2068 J. Gettys Category: Standards Track Compaq/W3C J. C. Mogul Compaq H. Frystyk W3C/MIT L. Masinter Xerox P. Leach Microsoft T. Berners-Lee W3C/MIT June, 1999 Hypertext Transfer Protocol -- HTTP/1.1 Status of this Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the “Internet Official Protocol Standards” (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. Copyright Notice Copyright (C) The Internet Society (1999). All Rights Reserved. Abstract The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. It is a generic, stateless, protocol which can be used for many tasks beyond its use for hypertext, such as name servers and distributed object management systems, through extension of its request methods, error codes and headers [47]. A feature of HTTP is the typing and negotiation of data representation, allowing systems to be built independently of the data being transferred. HTTP has been in use by the World-Wide Web global information initiative since 1990. This specification defines the protocol referred to as “HTTP/1.1”, and is an update to RFC 2068 [33]. Fielding, et al Standards Track [Page 1] RFC 2616 HTTP/1.1 June, 1999 Table of Contents HYPERTEXT TRANSFER PROTOCOL -- HTTP/1.1.................................................1
    [Show full text]