[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: Why ldap_<first,next>_attribute ?

To: MALCOLM BOFF <Malcolm_Boff@compuserve.com>
Subject: Re: Why ldap_<first,next>_attribute ?
From: Christopher Lakey <topher@pobox.com>
Date: Wed, 25 Feb 1998 09:38:23 -0600
Cc: Mark Smith <mcs@netscape.com>, Hallvard B Furuseth <h.b.furuseth@usit.uio.no>, "[unknown]" <ldap@umich.edu>, "[unknown]" <ietf-ldapext@netscape.com>
Delivered-to: ldapext-archive@critical-angle.com
References: <199802250814_MC2-349E-BB0C@compuserve.com>
Resent-date: Wed, 25 Feb 1998 07:36:48 -0800 (PST)
Resent-from: ietf-ldapext@netscape.com
Resent-message-id: <"sKK-m2.0.Z83.Eg3zq"@glacier>
Resent-sender: ietf-ldapext-request@netscape.com

For those not familiar with the iterator pattern, used in many software
systems, take a look at "Design Patterns: Elements of Reusable Object
Oriented Programming". 

What is a pattern? Visit the patterns homepage.

http://hillside.net/patterns/patterns.html

-- 
Christopher Lakey				Physitron Inc.
mailto:topher@pobox.com				Huntsville, AL
http://www.pobox.com/~topher/			(205) 534-4844

References:
- Re: Why ldap_<first,next>_attribute ?
  - From: MALCOLM BOFF <Malcolm_Boff@compuserve.com>

Prev by Date: Re: Why ldap_<first,next>_attribute ?
Next by Date: Re: Why ldap_<first,next>_attribute ?
Index(es):
- Chronological
- Thread