Deploying OpenLDAP
Welcome to the world of directories. Much like the fabled database administrator, you’ll be walking into a realm of often-complex data structures, mangled sources of information, and a buzzword-happy executive wanting to push your infrastructure into uncharted territory. Fortunately, many others...
Đã lưu trong:
| Tác giả chính: | |
|---|---|
| Định dạng: | Sách |
| Ngôn ngữ: | English |
| Được phát hành: |
Apress
2012
|
| Những chủ đề: | |
| Truy cập trực tuyến: | http://scholar.dlu.edu.vn/thuvienso/handle/DLU123456789/30978 |
| Các nhãn: |
Thêm thẻ
Không có thẻ, Là người đầu tiên thẻ bản ghi này!
|
| Thư viện lưu trữ: | Thư viện Trường Đại học Đà Lạt |
|---|
| id |
oai:scholar.dlu.edu.vn:DLU123456789-30978 |
|---|---|
| record_format |
dspace |
| spelling |
oai:scholar.dlu.edu.vn:DLU123456789-309782014-01-20T06:33:25Z Deploying OpenLDAP Jackiewicz., Tom Technologies Welcome to the world of directories. Much like the fabled database administrator, you’ll be walking into a realm of often-complex data structures, mangled sources of information, and a buzzword-happy executive wanting to push your infrastructure into uncharted territory. Fortunately, many others have already gone down this path and have already made the initial mistakes for you. A directory is basically a subset of the all-too-generic term database. It’s a specialized database with well-known methods of accessing and presenting information. Essentially, it’s a simple database used to hold straightforward information that’s accessed by simple methods from easy-to-understand clients written using solid, yet basic, programming interfaces. Directories, in the generic sense, have gone wherever the implementers’ imaginations have taken them. In the beginning, a database or some source of information was used for straightforward lookups for a single, simple task. That is, some applications required the ability to maintain data and, without input (or guidance) for any place, create a general format that fit its particular need—and only its particular need. These are application-specific directories. Vendors have their own methods of implementing and storing this data. An example in use today is the Name and Address Book in Lotus Notes. In a really bad scenario, these could just be text files that store local information in a format that only the parent application can use. One of the key limitations of these directories is the inability to share information between different systems. When information is updated in a directory containing a person’s employee status, for example, it would have to be updated across multiple environments. Lightweight Directory Access Protocol (LDAP) and directories in general have been optimized for the various tasks I’ll be discussing. They give you higher performance on reads and on retrieving data than they would on writes. Therefore, certain dynamic information (that requires a significant amount of updating) isn’t the best candidate for storage within LDAP.ie 2012-06-08T09:11:10Z 2012-06-08T09:11:10Z 2005 Book 1-59059-413-4 http://scholar.dlu.edu.vn/thuvienso/handle/DLU123456789/30978 en application/pdf Apress |
| institution |
Thư viện Trường Đại học Đà Lạt |
| collection |
Thư viện số |
| language |
English |
| topic |
Technologies |
| spellingShingle |
Technologies Jackiewicz., Tom Deploying OpenLDAP |
| description |
Welcome to the world of directories. Much like the fabled database administrator, you’ll be
walking into a realm of often-complex data structures, mangled sources of information, and
a buzzword-happy executive wanting to push your infrastructure into uncharted territory.
Fortunately, many others have already gone down this path and have already made the initial
mistakes for you.
A directory is basically a subset of the all-too-generic term database. It’s a specialized
database with well-known methods of accessing and presenting information. Essentially, it’s
a simple database used to hold straightforward information that’s accessed by simple methods
from easy-to-understand clients written using solid, yet basic, programming interfaces.
Directories, in the generic sense, have gone wherever the implementers’ imaginations have
taken them. In the beginning, a database or some source of information was used for straightforward
lookups for a single, simple task. That is, some applications required the ability to
maintain data and, without input (or guidance) for any place, create a general format that fit
its particular need—and only its particular need. These are application-specific directories.
Vendors have their own methods of implementing and storing this data. An example in use
today is the Name and Address Book in Lotus Notes. In a really bad scenario, these could just
be text files that store local information in a format that only the parent application can use.
One of the key limitations of these directories is the inability to share information between
different systems. When information is updated in a directory containing a person’s employee
status, for example, it would have to be updated across multiple environments. Lightweight
Directory Access Protocol (LDAP) and directories in general have been optimized for the various
tasks I’ll be discussing. They give you higher performance on reads and on retrieving data
than they would on writes. Therefore, certain dynamic information (that requires a significant
amount of updating) isn’t the best candidate for storage within LDAP.ie |
| format |
Book |
| author |
Jackiewicz., Tom |
| author_facet |
Jackiewicz., Tom |
| author_sort |
Jackiewicz., Tom |
| title |
Deploying OpenLDAP |
| title_short |
Deploying OpenLDAP |
| title_full |
Deploying OpenLDAP |
| title_fullStr |
Deploying OpenLDAP |
| title_full_unstemmed |
Deploying OpenLDAP |
| title_sort |
deploying openldap |
| publisher |
Apress |
| publishDate |
2012 |
| url |
http://scholar.dlu.edu.vn/thuvienso/handle/DLU123456789/30978 |
| _version_ |
1757669734968459264 |