590 likes | 604 Views
Explore the fundamentals of computer networks, protocols, Ethernet, the Internet, and web technologies. Learn about layers, addressing, routing, and the history of the Internet. Discover how devices communicate and exchange information in the digital world.
E N D
Introduction to Computing and Programming in Python: A Multimedia Approach Chapter 11: Advanced Text Techniques: Web and Information
Networks: Two or more computers communicating • Networks are formed when distinct computers communicate via some mechanism. • Rarely does the communication take the place of 0/1 voltages over a wire. • Too hard to make work over distances • More common is the use of frequencies (maybe in the sound range, but maybe not). • For example, a modem (modulator-demodulator) takes your computer’s 0’s and 1’s and translates them into sound frequencies that can pass over the sound wire and be decoded on the other side.
Networks, networks everywhere • If you’re driving a newer car, you probably have a network in there. • There are lots of computers in your car (controlling air flow, gas flow; making the air bag work) and they communicate. • You can have a network in your own home, or even on an airplane. • Can use radio signals for communication (wireless) • Or can string a cable between two computers.
Networks have layers • Networks have several layers to them. • At the bottom level is the physical substrate. • What are the signals being passed on? • Levels higher determine how data is encoded. • Do we use sound frequencies to represent 0’s and 1’s, or radio waves? • Do we send a bit at a time? A byte at a time? Or in packets larger than that? • Levels even higher determine the protocol of communication. • How do I address a particular computer I want to talk to? Or many computers? • How do I tell a computer that I want to talk to it? That I’m starting to send it data? What it’s supposed to do with it? When we’re done?
Ethernet: A common mid-level protocol • Ethernet is a common mid-level protocol. • It specifies some aspects of how data is encoded and computers are specified. • For example, each computer on an Ethernet network has a deep-down inside-the-computer address that identifies it uniquely. • But Ethernet can work over a variety of physical substrates. • For example, you can run Ethernet over wireless (radio) or over coaxial cable (where you hear terms like “10baseT”
Internet: A collection of networks • The Internet is a network of networks. • If you put a device in your home so that your computers can talk to one another, you have a network. • A wireless base station, or an Ethernet router, perhaps. • You can probably reach printers on your network, or copy files between computers. • If you now connect your network (through an Internet Service Provider (ISP)) to the global Internet, your network becomes yet another part of the whole Internet.
Internet is based on agreements on encodings • The Internet is built on a set of agreements about: • How computers will be addressed • A set of four numbers (each one byte now, soon to grow) separated by periods, e.g., 10.1.0.5. • A way of associating domainnames with these numbers, like www.cnn.com (which really is a name that resolves to a set of four numbers), using domain name servers. • How computers will communicate • That data will be put into packets with various pieces in them. • That computers will format their data and talk to one another using TCP/IP • How packets are routed around the network to find their destination.
The Internet is not new • The Internet agreements date back 40 years. • It was originally set up for military applications. • One of the features of the Internet is that packets find their destination even if part of the Internet is destroyed, damaged, or subject to censorship. • The Internet originally had only a handful of computers (nodes) on it, but it has grown dramatically in recent years.
Protocols on the Internet • But all that just lets us pass data back and forth. • What does the data say? • What does the data do? • One of the first applications placed on top of the Internet was electronic mail. • The mail protocols have evolved over time to their standard forms today. • The File Transfer Protocol (FTP) allows computers to move files between each other. • It defines what one side says to the other when copying a file over (e.g., “STO filename”) and how the file will be encoded.
Then there’s the Web • The Web dates only back to the 1980’s, but before there were graphical browsers (like Netscape Navigator, Internet Explorer, and the first, NCSA Mosaic). • The Web is (again) a set of agreements, started by Tim Berners-Lee • On how to refer to everything on the Internet: The URL (Uniform Resource Locator) • On how to create documents that refer to things all over the Internet: HTTP (HyperText Transfer Protocol) • On how those documents will be formatted: Using HTML (HyperText Markup Language)
HyperText: Non-linear text • Hypertext is a term invented by Ted Nelson in the 1960’s. • It refers to text that is non-linear, which the computer makes possible. • You’re familiar with this on the Web: • Read a little on a page, • Click, • Continue reading on some other page anywhere on the Internet.
The point of the Web is Hypertext • Tim Berners-Lee wanted a way to create readable documents that could reference material anywhere on the Internet in a hypertext format. • There are technical flaws in what he did: • For example, the phenomena of “dead links” couldn’t happen in other hypertext systems before the Web. • But it worked and has become a worldwide standard.
HyperText Transfer Protocol (HTTP) • HTTP defines a very simple protocol for how to exchange information between computers. • It defines the pieces of the communication. • What resource do you want? • Where is it? • Okay, here’s the type of thing it is (JPEG, HTML, whatever), and here it is. • And the words that the computers say to one another: • Not-complex words like “GET”, “PUT” and “OK”
Uniform Resource Locators (URL) • URLs allow us to reference any material anywhere on the Internet. • Strictly speaking, any computer providing a protocol accessible via URL. • Just putting your computer on the Internet does not mean that all of your files are accessible to everyone on the Internet. • URLs have four parts: • The protocol to use to reach this resource, • The domain name of the computer where the resource is, • The path on the computer to the resource, • And the name of the resource.
Example URLs http://www.cc.gatech.edu/index.html Protocol Domain name Path Filename ftp://cleon.cc.gatech.edu/pub/guzdial/papers/sigcse2003.pdf
What if there is no path? • Web servers (programs that understand the HTTP protocol) typically have a special directory that they serve from. • Files in that special directory are directly referable without specifying a path. • Sub-directories within the server directory can be accessed in terms of a path. • But always starting from the server directory, so not everything on your computer is always accessible.
A browser is a client • Your Web browser is called a client accessing a Web server. • Programs like Internet Explorer or Firefox or Safari understand a lot about Internet protocols. • They know how to interpret HTML and display it graphically. • If the HTML references other resources, like JPEG pictures, the client fetches them and displays them where appropriate. • Your client knows the details of the HTTP (and maybe FTP, mailto, gopher…) protocols so that it can request the resources you request.
You don’t need a browser to use the Internet • Your mail program also understands some Internet protocols. • JES even knows a little about one of the mail protocols, SMTP (Simple Mail Transfer Protocol), so that it can email homework to your instructor (if it’s set up). • Python (and other languages) have modules that allow you to use these protocols. • In Python, we can read any URL as if it was a file.
Opening a URL and reading it >>> import urllib >>> connection = urllib.urlopen("http://www.ajc.com/weather") >>> weather = connection.read() >>> connection.close()
Storing a file is different • It is possible to send information to a Web server. • That’s how search functions, forms, etc. work. • But it’s more complicated than just reading,and it requires an accepting program on the Web server. • It isn’t hard to send information to an FTP server, though. • But first, let’s make our temperature-finding function useful by directly reading the Weather page…
def findTemperatureLive(): # Get the weather page import urllib #Could go above, too connection=urllib.urlopen("http://www.ajc.com/weather") weather = connection.read() connection.close() #weatherFile = getMediaPath("ajc-weather.html") #file = open(weatherFile,"rt") #weather = file.read() #file.close() # Find the Temperature curloc = weather.find("Currently") if curloc <> -1: # Now, find the "<b>°" following the temp temploc = weather.find("<b>°",curloc) tempstart = weather.rfind(">",0,temploc) print "Current temperature:",weather[tempstart+1:temploc] if curloc == -1: print "They must have changed the page format -- can't find the temp" Getting the temperature live
Running it >>> findTemperatureLive() Current temperature: 57
FTP and HTTP Servers • FTP allows us to move files between computers on the Internet • Including our computer and the computer hosting our HTTP server. • Computers running HTTP servers often also run FTP servers to allow for manipulation of the Web files. • You can do this with specialized FTP clients, or with Python/Jython.
Uploading to an FTP server >>> import ftplib >>> connect = ftplib.FTP("cleon.cc.gatech.edu") >>> connect.login("guzdial",“mypassword") '230 User guzdial logged in.' >>> connect.storbinary("STOR barbara.jpg",open(getMediaPath("barbara.jpg"))) '226 Transfer complete.' >>> connect.storlines("STOR JESintro.txt",open("JESintro.txt")) '226 Transfer complete.' >>> connect.close()
The Interactive Web • The first use of HTTP was just to send around static pages and images (and sounds and…) • Later extensions allowed for users providing input to the server (such as for doing searches). • Originally, this was just “CGI” (Common Gateway Interface) scripts. • Later, servlets and applets and PHP and…
Interactive Web requires programs to generate HTML • Typically, a Web server will have some directory specified “special.” • Files referenced there aren’t just returned to the client. • Instead, the files are executed and the result is returned to the input. • There’s even a mechanism where the client can provide input to the executed files, e.g., a search string. • Those special files would generateHTML. • The generated HTML might be based on up-the-minute information like stock quotes and temperature sensors and database queries. • Thus, to have an interactive Web, we need to write programs that write HTML.
Using text to map between any media • We can map anything to text. • We can map text back to anything. • This allows us to do all kinds of transformations: • Sounds into Excel, and back again • Sounds into pictures. • Pictures and sounds into lists (formatted text), and back again.
Why care about media transformations? • Transformed digital media can be more easily transmitted • For example, transfer of binary files over email is often accomplished by converting to text. • We can encode additional information to check for and even correct errors in transmission. • It may allow us to use the media in new contexts, like storing it in databases. • Some transformations of media are made easier when the media are in new formats.
Mapping sound to text • Sound is simply a series of numbers (sample values). • To convert them to text means to simply create a long series of numbers. • We can store them to a file to manipulate them elsewhere.
Copying a sound to text def soundToText(sound,filename): file = open(filename,"wt") for s in getSamples(sound): file.write(str(getSample(s))+"\n") file.close()
What to do with sound as text • What this leaves us with is a long file, containing just numbers. • What knows how to deal with long lists of numbers? • EXCEL! • We can simply open our text (.txt) file in Excel.
We can process the sound in Excel • We can graph the sound (below) • A signal view is simply the graph of the sample values! • We can add a column and do some modification to the original sound. (Fill down to get them all.) • Can increase the volume that way.
Reading text back into a sound • After we process the sound (as text) in Excel, we can save it back to a sound. • First, copy the column you want into a new worksheet • Then, save the worksheet as a .txt file. • Get the full pathname of the new .txt file to use in JES.
Issues in reading the text back into a sound • We can’t be sure how many numbers are in the file. • We can’t be sure that the numbers will all fit into the sound we’ve chosen to serve as our target. • What we want to do is: • AS LONG AS we’re not out of numbers in the file, and AS LONG AS we still have room in the sound, • Copy a number out of the file, • And put it into a sample in the sound, • Then go to the next number and the next sample.
Reading the text back as a sound def textToSound(filename): #Set up the sound sound = makeSound(getMediaPath("sec3silence.wav")) soundIndex = 1 #Set up the file file = open(filename,"rt") contents=file.readlines() file.close() fileIndex = 0 # Keep going until run out sound space or run out of file contents while (soundIndex < getLength(sound)) and (fileIndex < len(contents)): sample=float(contents[fileIndex]) #Get the file line setSampleValueAt(sound,soundIndex,sample) fileIndex = fileIndex + 1 soundIndex = soundIndex + 1 return sound
while (soundIndex < getLength(sound)) and (fileIndex < len(contents)): • Let’s explain this statement: • while – keeps executing the block until the logical expression is false. • (soundIndex < getLength(sound)) – while the index is not yet at the end of the sound, so there’s still room for more numbers. • and – both parts have to be true for the whole thing to be true. • (fileIndex < len(contents)) – while there are any numbers left in the file, i.e., the fileIndex is before the length of the contents of the file.
We could do pictures, but more complicated • Pictures aren’t just a single number for each pixel • To recreate a picture in text we need to record, for each pixel: • The X and Y positions • The R, G, and B component values • That requires more structured text than simply a long line of numbers. • Let’s do that in just a few minutes.
Mapping from text to anything • Once we’ve converted to text (or numbers), we can do anything we want. • Like, mapping from sound to…pictures!
We simply decide on a representation: How do we map sample values to colors? def soundToPicture(sound): picture = makePicture(getMediaPath("640x480.jpg")) soundIndex = 0 for p in getPixels(picture): if soundIndex == getLength(sound): break sample = getSampleValueAt(sound,soundIndex) if sample > 1000: setColor(p,red) if sample < -1000: setColor(p,blue) if sample <= 1000 and sample >= -1000: setColor(p,green) soundIndex = soundIndex + 1 return picture • Here’s one: • Greater than 1000 is red • Less than 1000 is blue • Everything else is green
Break • break is yet another new statement. • It literally means “Exit the current loop.” • It’s most often used in the block of an if • “If something extraordinary happens, leave the loop immediately.” • In this case, “If we run out of samples before we run out of pixels, STOP!”
Any visualization of any kind is merely an encoding • A line chart? A pie chart? A scatterplot? • These are just lines and pixels set to correspond to some mapping of the data • Sometimes data is lost • Recall the mapping of grayscale • Sometimes data is not lost, even if it looks like a dramatic change. • Recall creating a negative of an image, then taking the negative of a negative to get back to the original.
Lists can do anything! def soundToList(sound): list = [] for s in getSamples(sound): list = list + [getSample(s)] return list Going from sound to lists is easy:
This really does work >>> list = soundToList(sound) >>> print list[0] 6757 >>> print list[1] 6852 >>> print list[0:100] [6757, 6852, 6678, 6371, 6084, 5879, 6066, 6600, 7104, 7588, 7643, 7710, 7737, 7214, 7435, 7827, 7749, 6888, 5052, 2793, 406, -346, 80, 1356, 2347, 1609, 266, -1933, -3518, -4233, -5023, -5744, -7394, -9255, -10421, -10605, -9692, -8786, -8198, -8133, -8679, -9092, -9278, -9291, -9502, -9680, -9348, -8394, -6552, -4137, -1878, -101, 866, 1540, 2459, 3340, 4343, 4821, 4676, 4211, 3731, 4359, 5653, 7176, 8411, 8569, 8131, 7167, 6150, 5204, 3951, 2482, 818, -394, -901, -784, -541, -764, -1342, -2491, -3569, -4255, -4971, -5892, -7306, -8691, -9534, -9429, -8289, -6811, -5386, -4454, -4079, -3841, -3603, -3353, -3296, -3323, -3099, -2360]
Can we go from pictures into lists? • Of course! We just have to decide on a representation. • We’ll put a list as an element for each pixel. • The numbers in the pixel-list will represent • The X and Y positions • The Red, Green, and Blue component values.
Pictures to Lists def pictureToList(picture): list = [] for p in getPixels(picture): list = list + [[getX(p),getY(p),getRed(p),getGreen(p),getBlue(p)]] return list Why the double brackets? Because we’re putting a sub-list in the list, not just adding a component as we were with sound.
Running pictureToList >>> picture = makePicture(pickAFile()) >>> piclist = pictureToList(picture) >>> print piclist[0:5] [[1, 1, 168, 131, 105], [1, 2, 168, 131, 105], [1, 3, 169, 132, 106], [1, 4, 169, 132, 106], [1, 5, 170, 133, 107]]