lect07 - Lecture 7 Name and Directory Servers CDK Chapter 9...

Info icon This preview shows pages 1–9. Sign up to view the full content.

View Full Document Right Arrow Icon
Lecture 7: Name and Directory Servers CDK: Chapter 9 TVS: Chapter 5
Image of page 1

Info icon This preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
10 Oct 2016 Distributed Systems Lecture 7 2 Binding RPC Client to Server Not desirable to hardwire the machine name and port number used by a server into a client Use a directory server instead (to find machine) – directory server machine known Use a local daemon on that machine to find port to use (daemon uses known port)
Image of page 2
10 Oct 2016 Distributed Systems Lecture 7 3 Binding a Client to a Server TVS: Figure 4-13 Client-to-server binding in a Distributed Computing Environment (endpoint – commonly known as a port)
Image of page 3

Info icon This preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
10 Oct 2016 Distributed Systems Lecture 7 4 Names Pure names contain no information about the item they are associated with (Needham) Other names may either tell you what sort of object they refer to, or something about where it can be found An address is an extreme example of a non- pure name
Image of page 4
10 Oct 2016 Distributed Systems Lecture 7 5 Name resolution A name is resolved when it is translated into data about the item Names are bound to attributes (i.e. values of properties – such as addresses!) A name has a namespace or domain … You can compose names to make bigger ones (e.g. URLs)
Image of page 5

Info icon This preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
10 Oct 2016 Distributed Systems Lecture 7 6 Composed naming domains used to access a resource from a URL URL Resource ID (IP number, port number, pathname) Network address 2:60:8c:2:b0:5a file 2:60:8c:2:b0:5a Web server 55.55.55.55 WebExamples/earth.html 8888 DNS lookup CDK Fig 9.1
Image of page 6
10 Oct 2016 Distributed Systems Lecture 7 7 URIs, URLs, and URNs U niform R esource I dentifiers identify resources on the Web. Start by identifying the URI scheme – e.g. http:, ftp:, etc. U niform R esource L ocators – a subset of URIs which give a location for a resource U niform R esource N ames – URIs which are not URLs, e.g. urn:ISBN:0-201-62433-8
Image of page 7

Info icon This preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
10 Oct 2016 Distributed Systems Lecture 7 8 Namespaces Can be flat (e.g. a number, a string)
Image of page 8
Image of page 9
This is the end of the preview. Sign up to access the rest of the document.

{[ snackBarMessage ]}

What students are saying

  • Left Quote Icon

    As a current student on this bumpy collegiate pathway, I stumbled upon Course Hero, where I can find study resources for nearly all my courses, get online help from tutors 24/7, and even share my old projects, papers, and lecture notes with other students.

    Student Picture

    Kiran Temple University Fox School of Business ‘17, Course Hero Intern

  • Left Quote Icon

    I cannot even describe how much Course Hero helped me this summer. It’s truly become something I can always rely on and help me. In the end, I was not only able to survive summer classes, but I was able to thrive thanks to Course Hero.

    Student Picture

    Dana University of Pennsylvania ‘17, Course Hero Intern

  • Left Quote Icon

    The ability to access any university’s resources through Course Hero proved invaluable in my case. I was behind on Tulane coursework and actually used UCLA’s materials to help me move forward and get everything together on time.

    Student Picture

    Jill Tulane University ‘16, Course Hero Intern