Edge Rewrite
// HTMLRewriter · presentation

This page was redesigned at the edge.

Cloudflare fetched the original article and streamed it through HTMLRewriter to apply an entirely new visual system without rebuilding the source page.

// request.cf · coarse context

A page that knows where it met you.

Only coarse request metadata is shown. This demo does not display or persist visitor IP addresses.

Country
US
Cloudflare location
CMH
Connection
HTTP/2
Language
Not provided

Ray ID: a224b71b58417089

Jump to content

Directory Assistance Service

From Wikipedia, the free encyclopedia

The Directory Assistance Service (DAS) is an obsolete protocol and service for accessing X.500 directory services. DAS was intended to provide a lightweight means for clients to access X.500 directory services via a split-Directory User Agent model. Here, the Directory User Agent (DUA) (the directory client) is split into a Directory Assistance (DA) client and a Directory Assistant. The directory user would interact with the DA-client, the DA-Client would communicate with the Directory Assistant using the DA protocol, and the Directory Assistant would communicate with the Directory Service using the X.500 Directory Access Protocol (DAP). That is, the Directory Assistant is a Directory Assistance protocol to DAP gateway. This design allows the DA-client to access the directory without requiring it to support the cumbersome Open Systems Interconnection protocol stack.

The Directory Assistance Service was created in 1990 by Marshall Rose while at Performance Systems International, Inc., and formally specified in RFC 1202 (published in 1991). It was an evolution of the DISH client/server interface in Quipu, developed by Colin Robbins while at University College London.

These and related efforts, such as DIXIE, led to the development of the Lightweight Directory Access Protocol.[1] LDAP replaced the Directory Assistance Service.

References

[edit]
  1. "Pre-History of LDAP". Cyber Matters. Retrieved 5 October 2014.