Why might a DNS client choose recursive navigation rather than iterative navigation? What is the
relevance of the recursive navigation option to concurrency within a name server?
What will be an ideal response?
A DNS client may choose recursive navigation simply because it is too basic to perform iterative navigation.
A server that performs recursive navigation must await a reply from another server before replying to the
client. It is preferable for a server to deal with several outstanding client requests at one time rather than
holding off other requests until each one is completed, so that clients are not unduly held up. The server will,
in general, refer resolution to several other servers rather than just one, so client requests will be satisfied in
parallel to some extent.
You might also like to view...
How do methods setIn, setOut and setErr affect the standard input, output and error streams?
a. They output data to the standard input, output and error streams. b. They provide the only way to access the standard input, output and error streams. c. They redirect the standard input, output and error streams. d. They empty the standard input, output and error streams.
Display the course number, number of sections and total capacity for courses having more than 3 sections.( 9 rows).
What will be an ideal response?
Clicking on the Text Effects button causes several text formatting options and a Text Effects ________ to appear
A) gallery B) data source C) prototype D) template
The lack of feedback is one disadvantage of Web-based training and distance learning.
Answer the following statement true (T) or false (F)