|
Connected: An Internet Encyclopedia
6.1.1. Control Up: Requests For Comments Up: RFC 1035 Up: 6. NAME SERVER IMPLEMENTATION Up: 6.1. Architecture Next: 6.1.2. Database
6.1.1. Control
A name server must employ multiple concurrent activities, whether they are implemented as separate tasks in the host's OS or multiplexing inside a single name server program. It is simply not acceptable for a name server to block the service of UDP requests while it waits for TCP data for refreshing or query activities. Similarly, a name server should not attempt to provide recursive service without processing such requests in parallel, though it may choose to serialize requests from a single client, or to regard identical requests from the same client as duplicates. A name server should not substantially delay requests while it reloads a zone from master files or while it incorporates a newly refreshed zone into its database.
Connected: An Internet Encyclopedia 6.1.1. Control |
|
Dies ist ein Mirror von Connected: An Internet Encyclopedia von Brent Baccala. Die offizielle Projekt-Homepage findet sich im Web unter www.freesoft.org/CIE. Dieser Mirror wurde zuletzt aktualisiert am Samstag, 28 Januar 2006 18:17 +0100. |