22 Pages

Chapter4b

Course: COSC 4377, Fall 2008
School: U. Houston
Rating:
 
 
 
 
 

Word Count: 2085

Document Preview

4377, COSC Spring 2001 - Chapter 4b 4/4/01 IP datagram format IP protocol version number header length (bytes) "type" of data max number remaining hops (decremented at each router) upper layer protocol to deliver payload to 32 bits ver head. type of len service length fragment 16-bit identifier flgs offset time to upper Internet live layer checksum 32 bit source IP address 32 bit destination IP...

Register Now

Unformatted Document Excerpt

Coursehero >> Texas >> U. Houston >> COSC 4377

Course Hero has millions of student submitted documents similar to the one
below including study guides, practice problems, reference materials, practice exams, textbook help and tutor support.

Course Hero has millions of student submitted documents similar to the one below including study guides, practice problems, reference materials, practice exams, textbook help and tutor support.
4377, COSC Spring 2001 - Chapter 4b 4/4/01 IP datagram format IP protocol version number header length (bytes) "type" of data max number remaining hops (decremented at each router) upper layer protocol to deliver payload to 32 bits ver head. type of len service length fragment 16-bit identifier flgs offset time to upper Internet live layer checksum 32 bit source IP address 32 bit destination IP address Options (if any) E.g. timestamp, record route taken, pecify list of routers to visit. total datagram length (bytes) for fragmentation/ reassembly data (variable length, typically a TCP or UDP segment) 4: Network Layer 4b-1 IP Fragmentation & Reassembly network links have MTU (max.transfer size) - largest possible link-level frame. r different link types, different MTUs large IP datagram divided ("fragmented") within net r one datagram becomes several datagrams r "reassembled" only at final destination r IP header bits used to identify, order related fragments fragmentation: in: one large datagram out: 3 smaller datagrams reassembly 4: Network Layer 4b-2 1 COSC 4377, Spring 2001 - Chapter 4b 4/4/01 IP Fragmentation and Reassembly length ID fragflag offset =4000 =x =0 =0 One large datagram becomes several smaller datagrams length ID fragflag offset =1500 =x =1 =0 length ID fragflag offset =1500 =x =1 =1480 length ID fragflag offset =1040 =x =0 =2960 4: Network Layer 4b-3 ICMP: Internet Control Message Protocol used by hosts, routers, gateways to communication network-level information r error reporting: unreachable host, network, port, protocol r echo request/reply (used by ping) network-layer "above" IP: r ICMP msgs carried in IP datagrams ICMP message: type, code plus first 8 bytes of IP datagram causing error Type 0 3 3 3 3 3 3 4 8 9 10 11 12 Code 0 0 1 2 3 6 7 0 0 0 0 0 0 description echo reply (ping) dest. network unreachable dest host unreachable dest protocol unreachable dest port unreachable dest network unknown dest host unknown source quench (congestion control - not used) echo request (ping) route advertisement router discovery TTL expired bad IP header 4: Network Layer 4b-4 2 COSC 4377, Spring 2001 - Chapter 4b 4/4/01 Routing in the Internet The Global Internet consists of Autonomous Systems (AS) interconnected with each other: r r r Stub AS: small corporation Multihomed AS: large corporation (no transit) Transit AS: provider Two-level routing: r r Intra-AS: administrator is responsible for choice Inter-AS: unique standard 4: Network Layer 4b-5 Internet AS Hierarchy Intra-AS border (exterior gateway) routers Inter-AS interior (gateway) routers 4: Network Layer 4b-6 3 COSC 4377, Spring 2001 - Chapter 4b 4/4/01 Intra-AS Routing Also known as Interior Gateway Protocols (IGP) Most common IGPs: r r r RIP: Routing Information Protocol OSPF: Open Shortest Path First IGRP: Interior Gateway Routing Protocol (Cisco propr.) 4: Network Layer 4b-7 RIP ( Routing Information Protocol) Distance vector algorithm Included in BSD-UNIX Distribution in 1982 Distance metric: # of hops (max = 15 hops) r Can you guess why? Distance vectors: exchanged every 30 sec via Response Message (also called advertisement) Each advertisement: route to up to 25 destination nets 4: Network Layer 4b-8 4 COSC 4377, Spring 2001 - Chapter 4b 4/4/01 RIP (Routing Information Protocol) z w A x D C Destination Network B y w y z x Next Router .... A B B -.... Num. of hops to dest. 2 2 7 1 .... Routing table in D 4: Network Layer 4b-9 Figure 13-3 Example of updating a routing table RIP message from C Net2 4 Net3 8 Net6 4 Net8 3 Net9 5 Old routing table Net1 Net2 Net6 Net8 Net9 7 2 8 4 4 A C F E F RIP message from C after increment Net2 5 Net3 9 Net6 5 Net8 4 Net9 6 Updating algorithm New routing table Net1 7 Net2 5 Net3 9 Net6 5 Net8 4 Net9 4 A C C C E F Rules Net1: No news, don't change Net2: Same next hop, replace Net3: A new router, add Net6: Different next hop, new hop count smaller, replace Net8: Different next hop, new hop count the same, don't change Net9: Different next hop, new hop count larger, don't change 4: Network Layer 4b-10 5 COSC 4377, Spring 2001 - Chapter 4b 4/4/01 Figure 13-4 Initial routing table in a small autonomous system 14 1 -- 55 1 -- 14 1 -- 23 1 -- 78 1 -- A Net: 78 F Net: 23 Net: 14 B Net: 55 55 1 -- 66 1 -- C 78 1 -- 92 1 -- Net: 92 Net: 66 E 08 1 -- 23 1 -- Net: 08 08 1 -- 66 1 -- D 4: Network Layer 4b-11 Figure 13-5 Final routing tables for the previous figure 08 14 23 55 66 78 92 2 E 1 -- 1 -- 2 B 3 E 1 -- 2 F A Net: 14 08 14 23 55 66 78 92 3 1 2 1 2 2 3 A -- A -- C A A B Net: 55 08 14 23 55 66 78 92 2 2 3 1 1 3 4 C D B D -- -- B B Net: 78 F Net: 23 08 14 23 55 66 78 92 3 2 2 3 4 1 1 A A A A A -- -- Net: 92 Net: 66 E 08 14 23 55 66 78 92 1 2 1 3 2 2 3 -- A -- A D A A Net: 08 08 14 23 55 66 78 92 1 3 2 2 1 3 4 D -- E E C -- E E 4: Network Layer 4b-12 6 COSC 4377, Spring 2001 - Chapter 4b 4/4/01 RIP: Link Failure and Recovery If no advertisement heard after 180 sec --> neighbor/link declared dead r routes via neighbor invalidated r new advertisements sent to neighbors r neighbors in turn send out new advertisements (if tables changed) r link failure info quickly propagates to entire net r poison reverse used to prevent ping-pong loops (infinite distance = 16 hops) 4: Network Layer 4b-13 RIP Table processing RIP routing tables managed by application-level process called route-d (daemon) advertisements sent in UDP packets, periodically repeated 4: Network Layer 4b-14 7 COSC 4377, Spring 2001 - Chapter 4b 4/4/01 RIP Table example (continued) Router: giroflee.eurocom.fr Destination -------------------127.0.0.1 192.168.2. 193.55.114. 192.168.3. 224.0.0.0 default Gateway Flags Ref Use Interface -------------------- ----- ----- ------ --------127.0.0.1 UH 0 26492 lo0 192.168.2.5 U 2 13 fa0 193.55.114.6 U 3 58503 le0 192.168.3.5 U 2 25 qaa0 193.55.114.6 U 3 0 le0 193.55.114.129 UG 0 143454 Three attached class C networks (LANs) Router only knows routes to attached LANs Default router used to "go up" Route multicast address: 224.0.0.0 Loopback interface (for debugging) 4: Network Layer 4b-15 Figure 13-10 Slow convergence 0 seconds 15 seconds n 15 seconds ... R1 Net1 Net2 R2 ... Rn Net n + 1 4: Network Layer 4b-16 8 COSC 4377, Spring 2001 - Chapter 4b 4/4/01 Figure 13-11 Hop counts R1 Net1 Net2 R2 Total hop count should be less than 16 ... Rn Net n + 1 4: Network Layer 4b-17 OSPF (Open Shortest Path First) "open": publicly available Uses Link State algorithm r r r LS packet dissemination Topology map at each node Route computation using Dijkstra' algorithm s OSPF advertisement carries one entry per neighbor router Advertisements disseminated to entire AS (via flooding) 4: Network Layer 4b-18 9 COSC 4377, Spring 2001 - Chapter 4b 4/4/01 OSPF "advanced" features (not in RIP) Security: all OSPF messages authenticated (to prevent malicious intrusion); TCP connections used Multiple same-cost paths allowed (only one path RIP) in For each link, multiple cost metrics for different TOS (eg, satellite link cost set "low" for best effort; high for real time) Integrated uni- and multicast support: r Hierarchical OSPF in large domains. Multicast OSPF (MOSPF) uses same topology data base as OSPF 4: Network Layer 4b-19 Hierarchical OSPF 4: Network Layer 4b-20 10 COSC 4377, Spring 2001 - Chapter 4b 4/4/01 Hierarchical OSPF Two-level hierarchy: local area, backbone. r Link-state advertisements only in area r each nodes has detailed area topology; only know direction (shortest path) to nets in other areas. Area border routers: "summarize" distances to nets in own area, advertise to other Area Border routers. Backbone routers: run OSPF routing limited to backbone. Boundary routers: connect to other ASs. 4: Network Layer 4b-21 IGRP (Interior Gateway Routing Protocol) CISCO proprietary; successor of RIP (mid 80s) Distance Vector, like RIP several cost metrics (delay, bandwidth, reliability, load etc) uses TCP to exchange routing updates Loop-free routing via Distributed Updating Alg. (DUAL) based on diffused computation 4: Network Layer 4b-22 11 COSC 4377, Spring 2001 - Chapter 4b 4/4/01 Inter-AS routing 4: Network Layer 4b-23 Internet inter-AS routing: BGP BGP (Border Gateway Protocol): the de facto standard Path Vector protocol: r similar to Distance Vector protocol r each Border Gateway broadcast to neighbors (peers) entire path (I.e, sequence of ASs) to destination r E.g., Gateway X may send its path to dest. Z: Path (X,Z) = X,Y1,Y2,Y3,... ,Z 4: Network Layer 4b-24 12 COSC 4377, Spring 2001 - Chapter 4b 4/4/01 Internet inter-AS routing: BGP Suppose: gateway X send its path to peer gateway W W may or may not select path offered by X r cost, policy (don' route via competitors AS), loop t prevention reasons. If W selects path advertised by X, then: Path (W,Z) = w, Path (X,Z) Note: X can control incoming traffic by controling it route advertisements to peers: r e.g., don' want to route traffic to Z -> don' t t advertise any routes to Z 4: Network Layer 4b-25 Figure 13-44 Path vector packets AS1 N1 AS2 R2 R1 N1 R1 AS1 N1 R2 AS2, AS1 N1 R3 AS3, AS2, AS1 R3 R4 AS4 AS3 4: Network Layer 4b-26 13 COSC 4377, Spring 2001 - Chapter 4b 4/4/01 Internet inter-AS routing: BGP BGP messages exchanged using TCP. BGP messages: r OPEN: opens TCP connection to peer and authenticates sender r UPDATE: advertises new path (or withdraws old) r KEEPALIVE keeps connection alive in absence of UPDATES; also ACKs OPEN request r NOTIFICATION: reports errors in previous msg; also used to close connection 4: Network Layer 4b-27 Why different Intra- and Inter-AS routing ? Policy: Inter-AS: admin wants control over how its traffic routed, who routes through its net. Intra-AS: single admin, so no policy decisions needed Scale: hierarchical routing saves table size, reduced update traffic Performance: Intra-AS: can focus on performance Inter-AS: policy may dominate over performance 4: Network Layer 4b-28 14 COSC 4377, Spring 2001 - Chapter 4b 4/4/01 Router Architecture Overview Two key router functions: run routing algorithms/protocol (RIP, OSPF, BGP) switching datagrams from incoming to outgoing link 4: Network Layer 4b-29 Input Port Functions Physical layer: bit-level reception Data link layer: e.g., Ethernet see chapter 5 Decentralized switching: given datagram dest., lookup output port using routing table in input port memory goal: complete input port processing at ` line speed' queuing: if datagrams arrive faster than forwarding rate into switch fabric 4: Network Layer 4b-30 15 COSC 4377, Spring 2001 - Chapter 4b 4/4/01 Input Port Queuing Fabric slower that input ports combined -> queueing may occur at input queues Head-of-the-Line (HOL) blocking: queued datagram at front of queue prevents others in queue from moving forward queueing delay and loss due to input buffer overflow! 4: Network Layer 4b-31 Three types of switching fabrics 4: Network Layer 4b-32 16 COSC 4377, Spring 2001 - Chapter 4b 4/4/01 Switching Via Memory First generation routers: packet copied by system' (single) CPU s speed limited by memory bandwidth (2 bus crossings per datagram) Input Port Memor...

Find millions of documents on Course Hero - Study Guides, Lecture Notes, Reference Materials, Practice Exams and more. Course Hero has millions of course specific materials providing students with the best way to expand their education.

Below is a small sample set of documents:

U. Houston - COSC - 4377
Slides from TCP/IP - ForouzanChapter 5Subnetting and Supernetting Subnetting Masking Examples of Subnetting Variable-Length Subnetting SupernettingForouzan NotesCOSC 6377 - Fall 20005-1Figure 5-1A network with two levels of hierarc
U. Houston - COSC - 4377
COSC 4377, Spring 2001 - Chapter 2, Part A9/18/01chapter 2: Application LayerChapter goals:conceptual + implementation aspects of network application protocols m client server paradigm m service models r learn about protocols by examining popul
U. Houston - COSC - 4377
COSC 4377, Spring 20011/24/01Protocol "Layers"Networks are complex! many "pieces": r hosts r routers r links of various media r applications r protocols r hardware, softwareIs there any hope of organizing structure of network? Or at least our
U. Houston - COSC - 4377
COSC 4377, Spring 20011/22/01Part I: IntroductionChapter goal: get context, overview, "feel" of networking more depth, detail later in course approach: r descriptive r use Internet as example Overview: what' the Internet s what' a protocol?
U. Houston - COSC - 4377
COSC 4377, Spring 2001 - Chapter 5b4/4/01LAN technologiesData link layer so far:rNext: LAN technologiesrservices, error detection/correction, multiple accessaddressing r Ethernet r hubs, bridges, switches r 802.11 r PPP r ATM5: DataLink
U. Houston - COSC - 4377
COSC 4377, Spring 2001 - Chapter 2, Part A1/29/01Chapter 2: Application LayerChapter goals: conceptual +implementation aspects of network application protocolsrMore chapter goals specific protocols:r r r r rhttpclient server paradigm
U. Houston - COSC - 4377
COSC 4377, Fall 2000 - Chapter 3b10/24/00TCP: Overview RFCs: 793, 1122, 1323, 2018, 2581point-to-point:rone sender, one receiverfull duplex data:rreliable, in-order byte steam:rrpipelined:rno message boundaries TCP conges
U. Houston - COSC - 4377
COSC 4377, Fall 2000 - Chapter18/29/00Part I: IntroductionChapter goal: get context, overview, feel of networking more depth, detail later in course approach: r descriptive r use Internet as example Overview: what the Internet s what a prot
U. Houston - COSC - 4377
COSC 4377, Fall 2000 - Chapter 4a10/26/00Chapter 4: Network LayerChapter goals: understand principlesChapter Overview:behind network layer services:r r r r network layer services routing principle: path instantiation androuting (pat
U. Houston - COSC - 4377
COSC 4377, Spring 20018/29/01Part I: IntroductionChapter goal: r get context, overview, "feel" of networking r more depth, detail later in course r approach: m descriptive m use Internet as example Overview: r what' the Internet s r what' a prot
U. Houston - COSC - 4377
COSC 4377, Fall 2000 - Chapter 2 Part B9/25/00DNS: Domain Name SystemPeople: many identifiers:rSSN, name, Passport #Domain Name System: distributed databaseInternet hosts, routers:rrIP address (32 bit) used for addressing datagrams
U. Houston - COSC - 4377
COSC 4377, Spring 2001 - Chapter 74/24/01Chapter 7: Network securityFoundations: Security in practice:what is security? cryptography authentication message integrity key distribution and certificationapplication layer: secure e-mail
U. Houston - COSC - 4377
COSC 4377, Spring 2001 - Chapter 5a4/4/01Chapter 5: The Data Link LayerOur goals: understand principlesOverview:behind data link layer services:r link layer services error detection, correction multiple access protocols andrr rer
U. Houston - COSC - 4377
Part I : I ntroductionC hapte goal: r ge conte ove w, "fe l" t xt, rvie e of ne tworking m de ore pth, de late in tail r course approach: r de scriptive r useI nte t as e rne xam ple Ove w: rvie what's theI nte t rne what's a protocol? ne twor
U. Houston - COSC - 4377
Errata=We all occasionally make mistakes. We're proud of the quality of ourtextbook, but in a first edition book with more than 700 pages, a coupleof typos are bound to slip in. The errata below lists the mistakes thatwe'll fix in the next pr
U. Houston - COSC - 6377
COSC 6377, Fall 200011/2/00HTTP Protocol, Proxy,andCOSC 6377 Term Project TutorialT. Mark Huang http:/www.cs.uh.edu/~jsteach/cosc6377/The Web: the http protocolhttp: hypertext transfer protocol Web application layer s protocol client/ser
U. Houston - COSC - 2
CS 4310 Programming Exercise Building a ParserDue Date: Midnight, Monday, Oct 23 Using bison, you are to write a parser for a subset of Pascal. A grammar for this language appears below: start block procdcls procdcl parmlist parms parm variables var
U. Houston - COSC - 4310
CS 4310 Programming Exercise Building a ParserDue Date: Midnight, Monday, Oct 23 Using bison, you are to write a parser for a subset of Pascal. A grammar for this language appears below: start block procdcls procdcl parmlist parms parm variables var
U. Houston - COSC - 4377
FAQ for Assignment #4, COSC 4377, Fall 2000Last update: Nov. 22, 20001) Do we have to use select()? [11/13/2000]A: No. I planned to use select() for this assignment. After I ran some sample programs and found that recvfrom() can take more t
U. Houston - COSC - 4377
COSC 4377, Fall 2000HW2HW2HW2UIDHW1discprogtotalHW3HW4MT#1MT#2FinalTotal===========ABE181201141349819570548274.80AKM8100451401859620070526272.05ASM269451071529818580427572.10BHM26620114
U. Houston - COSC - 4377
Bring a file under RCS control:RCS is a software tool for UNIX systems which lets people manage multiplerevisions of files. RCS saves all old revisions and does it in a spaceefficient way. Old revisions can be retrieved according to the revision
U. Houston - COSC - 4377
Bring a file under RCS control:RCS is a software tool for UNIX systems which lets people manage multiplerevisions of files. RCS saves all old revisions and does it in a spaceefficient way. Old revisions can be retrieved according to the revision
U. Houston - COSC - 4377
Chapter 4: Network LayerChapter goals: understand principlesOverview:selectionbehind network layer services:r r r r network layer services routing principle: path hierarchical routing IP Internet routing protocols instantiation andr
U. Houston - HW - 2
COSC 6318 Object-Oriented Analysis and DesignHomework #2Due: 5:15PM Feb. 28thFor the problem statement given below, 1. Draw a usecase diagram showing actors and usecases 2. Provide the flow of events for each use case, listing the basic paths
U. Houston - ASSIGN - 1
Assignment 1 Due Monday April 25th 6PM Homework #4 due Monday April 25th 6PM Feel free to ask any questions over the email. Please note that this is not a group effort. Assume that I am asked to write a middle tier (I am not required to writer the UI
U. Houston - HW - 3
Homework #3 Due April 19th 6PM in class. Name: _ Student ID: _A few problem statements are given below. For each one of them answer the following questions: (a). What creational pattern you may use to solve this problem? (b). Explain how you would
U. Houston - ASSIGN - 1
Assignment 1 Due Monday April 12th 6PM Online submission (Note: The online submission will refuse to accept assignments after the deadline You are asked to submit the assignment ahead of time and as many times as you please. Your last submission will
U. Houston - ASSIGN - 2
Assignment 2 email zip of all your code by 11:59PM May 9thThis is not a group project. Beware of the Academic Honesty Policy.Write a C+, Java or .NET program that will allow you to design a kitchen.The program presents a list of appliances you c
U. Houston - HW - 1
COSC 6318 HW1 Due Monday February 23th 5:45PM(Note. No late submissions will be accepted)Please turnin a hard copy in class. Remote students, please hand over thecopy to your remote site administrator by the deadline.Name: _ Student ID: _A
U. Houston - HW - 3
HW 3 Due April 18th 6PM1. What OO Design Principle is evident in the application of Iterator Pattern on different types of collections? 2. One major concern about implementing an interface to traverse through a collection is performance. Ho
U. Houston - HW - 1
COSC 6318 Object-Oriented Analysis and DesignSpring 2003Homework #1Due Feb. 19th 5:45PM in classDevelop the class diagram (in UML) for the following system. A "draw" utility program lets users draw several geometric objects on adiagr
U. Houston - HW - 4
HW4 Due Thursday April 30 7PM in classIn the Design Pattern text book on page 153, it reads"(C+) you want to hide the implementation of an abstraction completelyfrom clients. In C+ the representation of a class is visible inthe class interface
U. Houston - HW - 4
Homework 4 hard copy due April 22 5:45PMAnswer these questions based on your solution to Assignment 1.1. Draw a UML diagram showing the classes and the relationships.2. How did you provide extensibility in your program. 3. What design pri
U. Houston - HW - 5
Homework #5: Due Monday May 1st in class.1. Draw UML diagram for your solution in Assignment 2 questions 1.2. Draw UML diagram for your solution in Assignment 2 questions 2.3. Explain what are the benefits and disadavantages, with reference to
U. Houston - ASSIGN - 1
Assignment 1. Hard copy due on April 21st 5:45PM.Submit copy of all code you write.Problem. The objective of this assignment is to practise the useof some design patterns. You first need to identify what patterns will be useful in the following
U. Houston - HW - 3
COSC 6397 Object-Oriented Analysis and DesignSpring 1999Homework #3 Due Monday April 12th in classThe objective of this homework is to practice Inheritance and Polymorphism with OCP, LSP and DIP in mind. Several ty
U. Houston - HW - 5
Due along with your Assignment 2.Mention five recommendations from extreme programming.For each, write one or two sentences explaining thebenefit of the recommendation.
U. Houston - ASSIGN - 2
COSC 6318 Assignment 2. Due May 5th during demoYou are asked to build a library or module (in a languageof your choice: Java or C+). Your module will primarily consist of a bunch of classes to determine some ones credibility. Thecredibility may
U. Houston - HW - 3
COSC 6318 Object-Oriented Analysis and DesignHard copy HW3 Due March 27th in classGiven below is the use-case flow of events for a system. Develop the analysis model for this system, based on the given use-case. Present the following 1. Collab
U. Houston - HW - 3
COSC 6318 Object-Oriented Analysis and DesignHomework #3Due: 5:45PM April 2ndFor the problem stated in HW2, a use case model with the flow of eventsis given here. 1. Draw the collaboration diagrams for each flow of events.2. Draw a package
U. Houston - ASSIGN - 2
If you will be using C+, please use thegiven LegalStatus.h and LegalStatus.cpp.For other classes (Person, CreditRecords, CriminalRecords),please modify the code as you please from the Java directory.
U. Houston - ASSIGNMENT - 1
Assignment 1: Due October 2nd(Email code to Venkat by midnight and cc your buddy)In this assignment we will create a program to playMaster Mind.You are expected to create two parts. A Decoder class thatdeals with the logic (create it using tes
U. Houston - ASSIGN - 4
Assignment 4: Due 11:59PM May 11thFor the problem mentioned in Assignment 3 create the applicationwith following "features":1. Visiting the application at http:/localhost:3000 should bring upthe relevant page for books list2. This page must co
U. Houston - ASSIGNMENT - 4
Assignment 4: Due 11:59PM December 8thFor the problem mentioned in Assignment 3 create the applicationwith following "features":1. Visiting the application at http:/localhost:3000 should bring upthe relevant page for tasks2. This page must con
U. Houston - HW - 1
124 9 139 9 324 9 341 9 347 9 588 9 637 8 726 9 734 9 863 9 865 9 (Why would you inherit Person from StandardError?!)925 9 926 8 976 9 If you have questions, please talk to Venkat in Person.No emailes regarding grading p
U. Houston - ASSIGN - 2
124 100139 100 324 100341 90 Code has warnings. Not DRY - db definition in multiple files347 80 Search by keyword not in first level menu. Problems with multiple authors588 90 Search by author not functioning well637 100726 80 Search and filte
U. Houston - HW - 3
124 9 Multiple clicks on fetch not handled well139 10324 9 Multiple clicks on fetch not handled well341 10347 10588 10637 10726 5 Does not work as expected734 10863 10865 10925 10926 0 Quick look at submitted files does not point to solu
U. Houston - HW - 3
You lost points if1 - You have way too much code - should have used prototype, for instance.1 - Your code (any of the versions you submitted) does not work with IE 7.1 - Clicking multiple times on Fetch pollutes the table with redundant info (or
U. Houston - HW - 4
You lost points if- you did not provide adequate information- you did not include any or sufficient references
U. Houston - HW - 2
You lost points if you Did not close the test data file that you opened.You are accumulating quite a bit of data in a string - not elegant.
U. Houston - ASSIGNMENT - 2
If you lost points, the following may be reason(s)You're performing validation logic in a place other than the model.Some tests are failingDid not have any tests (for validation logic, for example)When run, your program says ".in `method_missi
U. Houston - SCHATZKES - 3242
Slideshow for Ketelsen Employees Who Use a Computer on CampusPlease ensure that your computer is protected from virus's. Follow this slide show for step by step instructions for downloading Trend Virus Protection1Instructions for downloading Tre
U. Houston - SCHATZKES - 3242
Ketelsen Elementaryy SchoolSeptember 13, 2006 Vo l u m e 1 , I s s u e 1 A l m a L a ra , P r i n c i p a l Jaqueline Green, Assistant Principal M a r l a L i n g l e , A d m i n i s t ra t i v e I n t e r nPrincipals NewsAfter School Program It
U. Houston - SCHATZKES - 6537
Peripherals INST 65371Peripherals INST 6537 Team 3 Sheila Schatzke- Primary Author Sahar Othman Joseph HamiltonShelia, You have a good basic list of peripherals, but seem to have concentrated a lot on printers and their supplies. When you say p
U. Houston - SCHATZKES - 65372
Peripherals INST 65371Peripherals INST 6537 Team 3 Sheila Schatzke- Primary Author Sahar Othman Joseph HamiltonShelia, You have a good basic list of peripherals, but seem to have concentrated a lot on printers and their supplies. When you say p
U. Houston - SCHATZKES - 6537
U. Houston - SCHATZKES - 65372
U. Houston - SCHATZKES - 6537
U. Houston - SCHATZKES - 65372
U. Houston - SCHATZKES - 6537
Sheila Schatzke Assignment 3.21Computer WorkstationsOptiPlex 170L Small Desktop: Operating System: File System: Memory: Keyboard: Monitors: Graphics Cards: Boot Hard Drive: Floppy: Mouse: Integrated Network Adapter (NIC): Removable Media Storage
U. Houston - SCHATZKES - 65372
Sheila Schatzke Assignment 3.21Computer WorkstationsOptiPlex 170L Small Desktop: Operating System: File System: Memory: Keyboard: Monitors: Graphics Cards: Boot Hard Drive: Floppy: Mouse: Integrated Network Adapter (NIC): Removable Media Storage