Persistent systems. Traditional software: Data stored outside of program. Program

Transcription

1 Persistent systems Traditional software: Data stored outside of program Program Persistent systems: Data part of program Execution never stops Transaction systems Program 1

2 Development of persistent languages 1. Data: Transient data: For life of one execution Persistent data: Exists across executions 2. Need a mechanism to indicate an object is persistent approach is to assume all data are transient and indicate which objects are persistent 3. Need a mechanism to address a persistent object The language can develop its own model of persistent storage 4. Need to synchronize simultaneous access to an individual persistent object Use of semaphores 5. Need to check type compatibility of persistent objects Because of the multiple programs that access persistent data, name equivalence is difficult to use, structural equivalence is the preferred method in persistent languages. 2

3 Client-server computing Evolution of computer technology: 1960s: Standalone mainframes. As machine speed increased, use of multiprogramming and time sharing 1970s: Development of less expensive personal computers 1980s: As personal computers evolved, need for centralized resources to collect and store data (e.g., to corporate database) Need for local area networks (LANs) Development of the ARPANET and Internet Need for communication protocols between computers Need for computing models to adapt to this 1990s: Interconnection and globalization of computing The World wide web and global access for all 3

4 Loosely coupled systems Each processor has its own memory and disk storage Communication lines to other processors to transfer information Leads to millisecond times to access data Synchronization harder - Machine communicating with may not be accessible on network because of a variety of reasons. Systems developed on such architectures are called distributed systems 4

5 Distributed systems Distributed systems can be centralized, where a single processor does the scheduling and informs the other machines as to the tasks to execute When completed, the assigned processor will indicate that it is ready to do another task distributed or peer-to-peer, where each machine is an equal and the process of scheduling is spread among all of the machines - one processor broadcasts a message to all the processors, and an inactive processor could respond with the message I'll do it. - Alternatively, each machine in the network will individually invoke a task on a specified machine elsewhere in the network. In this way, work gradually gets propagated around the network 5

6 Client-server mediator architecture 6

7 Client-server mediator architecture Client machine: Interacts with user Has protocol to communicate with server Server: Decides where data is located Accesses data Mediator is software that uses encoded knowledge about sets of data to create information for a higher class of application. Issues: May be communicating with multiple clients simultaneously Need to keep each such transaction separate Multiple local address spaces in server 7

8 Impact on language design Lack of a global data store for the program. Both the client and server only have limited access to the total information content of the program. Programs need to be divided into separate pieces to effectively compute an answer (e.g., tasks). The Remote Procedure Call (RPC)is another communication method. An RPC syntactically looks like a subprogram call except that the operating system will enact a program possibly on another processor. RPCs are related to message communication and often are implemented as a send-receive message strategy client sends an RPC message to a server server waits on a receive for the message then responds back to the client in a similar manner. 8

9 ARPANET Initial idea was by Defense Advanced Research Project Agency (DARPA) project in late 1960s for a national defense network began a project to see whether several computers, widely separated geographically, could be linked together to enable users at a terminal on one system to access the resources on another computer. Initial military concept: provide access to computers if some communications lines are destroyed by building a network where data communications traffic could dynamically adapt to changing conditions. data communications -sending messages reliably from one computer to another- was the major obstacle. The initial ARPANET began in 1970 as a three-node network linking BBN in Cambridge, Massachusetts, with UCLA and SRI in California using 56 kilobit lines. Sites added until several hundred by mid-1970s 9

10 ARPANET communications Communication between two computers was handled via messages. A message was broken down into fixed-length strings called packets, and the packets were sent from computer to computer until the original message was reassembled at the receiving node. To ensure that messages destined for another computer arrived reliably, a formal communication model - called a protocol -was developed. For the ARPANET, this developed as the Transmission Control Program/ Internet Protocol (TCP/IP). TCP/IP was a low-level communication mechanism that simply determined that a sequence of bytes destined for a specific computer arrived there uncorrupted. It was generally too complex for users to use directly for accessing a computer. 10

11 User protocols Telnet is a protocol that makes the sending computer - the computer the user is actually working on -behave like a terminal connected to the distant computer. - user is connected to a client computer, which acts like a terminal, and the terminal program is communicating using the telnet protocol to a distant host computer, which is providing the server program. SMTP is Simple Mail Transport Protocol. This provides the basic (electronic mail) that has become so ubiquitous today FTP is File Transfer Protocol. One would invoke the FTP client on a local machine, log onto the distant server machine using the FTP protocol, and then retrieve the desired documents from the distant machine or send documents from the user's machine to the distant machine. 11

12 Weaknesses in FTP one had to know explicitly which machine to access to retrieve the desired data. One also had to have access to the files of that machine to retrieve the information. The anonymous login partially solved that. One had to know exactly where on the file system the desired information was. Despite these weaknesses, FTP was the standard file transmission mechanism for many years until the web changed all that. 12

13 Birth of the Internet In the mid-1980s, ARPA decided to stop supporting the ARPANET. As a research activity, the concept had been proved, and ARPA was not in the business of providing what was becoming a commercial service. The U.S. National Science Foundation (NSF) took over the backbone network in the United States -the set of high-speed telephone lines that provided the basic TCP/IP communications traffic between host computers as a way to link universities together. The name of the network gradually evolved into the Internet. NSF support stopped. Attached to this backbone, local networks (a state, a university, a large company) were added until the Internet became this amorphous collection of computers all continually chattering to one another. Commercial providers, now called Internet Service Providers (ISP) established links to the Internet so that individuals on their home computers could use a modem to dial into their local ISP to be on the Internet. 13

14 The World Wide Web By the late 1980s, widespread interest to easily transfer files. FTP was a cumbersome process. Systems like gopher, archie, veronica developed Physicists -principally Tim Berners-Lee at CERN in Geneva -desired a mechanism to access and transfer documents by computer that was simpler than the standard FTP server. They developed the concept of a semantic description language. One server program would display a document, and a client program, called a browser, would read and understand the displayed document. The power of their system was that the displayed document contained pointers to other documents called hypertext. An earlier version of hypertext was Apple Computer's HyperCard product for the Macintosh, but the real power of the CERN development was to allow hypertext links to documents that existed on other computers connected to the Internet. 14

15 HTTP The protocol developed was the HyperText Transport Protocol (HTTP). Http an addition to TELNET, FTP, and SMTP protocols discussed earlier. Release of the first MOSAIC browser in 1993 led to rapid growth of the web. Each pointer became known as a Uniform Resource Locator (URL). Document location was reduced to: invoking a Web browser on your local machine, typing in a URL for the document you wanted to access, connecting to a Web server on the distant machine that contained the location of the typed in URL, displaying the document obeying the HTTP protocol. HTML language based upon SGML - to be explained later. 15

16 Web navigation 16

17 Prentice Hall example of navigation 1. The user types in the URL for the home page. This URL consists of: a Domain name ( and a file on that machine(users/mvz/pzbook). 2. The Web browser sends the domain name to one of several special Internet machines called Domain Name Servers} (DNS). The DNS returns the Internet Protocol address of the desired web page. 3. The web browser sends the file name to the Web server at IP address A HTTP Daemon (HTTPD) program on this machine is the main interface between a web server and the Internet. 4. The Web server appends the name index.html because the given file was a directory and not a file. 5. The contents of the file are sent back to the Web browser and displayed to the user. 6. If the user now clicks on the URL for Prentice-Hall that appears on the Web page ( the process is repeated and the Prentice-Hall server at IP address is accessed and the appropriate Web page is displayed. 17

18 Portals To make navigation easier, certain Web sites are now known as portals -entrance sites to the WWW. These sites have programs known as search engines. A search engine is a query processor in which you enter a question. The result of that query is a list of WWW locations that answer the question. Search engines often operate as Web crawlers. Beginning at one location, the Web crawler follows all links on that Web page to find other Web pages. 18

19 SGML Structured General Markup Language is basis of SGML an unstructured sequence of characters within the text can be SGML elements. The semantics of elements are unspecified, but their syntax is given. elements are bracketed by a start-tag and an end-tag notation. <zork> I am a zork </zork> identifies I am a zork as the contents of the zork element. A report in SGML: <report> <title} text </title> <author} text </author> <abstract} text </abstract> <body} text </body> </report> SGML handles semantic content, not presentation 19

20 HTML An instance of SGML with a defined syntax for Web pages <html> <title> title of document </title> <body> text of document </body> </html> Problem: SGML is semantic content, not layout (presentation). How to handle things like: <h1>major heading</h1> - What font and font size to use? - Where on page to place heading? Elements like <font size=...> move away from pure semantic content 20

21 Links in HTML HTML contains: Embedded text URLs: Links to other web pages < address> Images: <SRC SRC=...> MAILTO: protocol (Send ) Executable pages (CGI scripts. To be discussed soon) 21

22 HTML FORMS A method for passing information between a user at a Web browser and a Web server. This information is passed to a program on the server system. This is the Common Gateway Interface (CGI) file. Web servers typically have a specific cgi-bin directory containing these CGI programs. HTML forms are used: <form method= type action= location of cgi script to execute > text </form> Perl often used as language for such scripts 22

23 CGI script example 23

24 HTML for form <HTML> <HEAD> <TITLE>cgi-test</TITLE> </HEAD> <BODY> <p> This is a sample page to read two data items from the web page: <form action="cgi-bin/xaction" method=get> <p>first name=<input type=text name=xfirst size=10> <br>last name=<input type=text name=xlast size=20> <br> <input type=submit value=send> <input type=reset value=reset> </form> </BODY> Parameters passed as arguments xfirst and xlast </HTML> 24

25 Perl - CGI script #!/usr/bin/perl print Content-Type: text/html\n\n ; print <html><head>\n ; print <title>sample PERL script</title>\n ; print </head><body>\n ; print <p>query_string is $ENV{'QUERY_STRING'}\n ; foreach ( split( /&/, $ENV{'QUERY_STRING'}) ) { ( $key, $val ) = split( /=/, $_, 2 ); $tmp{$key} = $val; } print <p>first name is <b>$tmp{'xfirst'}</b>\n ; print <p>last name is <b>$tmp{'xlast'}</b>\n ; print </body></html>\n Perl program first reads parameters as xfirst&zlast from $ENV (environment) into QUERY_STRING Output of Perl is the syntax of an HTML page that is displayed 25

26 Java applets Issue: Many different protocols Solution: Send program to read protocol as part of HTML (Role for Java) Moves processing needs from HTML server to HTML cllient Do more processing on client side of web import java.awt.*; /* applet library */ public class hello extends java.applet.applet public void paint(graphics x) {x.drawstring( Hello World, 100, 100);} Displayed by: <html> <body> <applet code = hello.class width=200 height=200> </applet> </body> </html> 26