> Their accounts will be established through a Plone (Zope) site I'm > building. That's scenario #1. Scenario #2 has *no* accounts except for > my own. In that scenario, I'm simply accessing data and spitting it > out. Actually, there are two sub-scenarios here: (a) where a request > comes in for Web page, I translate the request to something that > corresponds to my document tree. The reason for this is because > certain SEs don't like deep doc trees, but a deep doc tree is > necessary for organizational purposes in my case. So I want to assign > a number to each doc, have that published to the outside world for the > sake of the SEs, then translate it internally to fetch the document; > (b) Many of the documents reference other outside docs in a standard > manner. These references are framed in tables, with unvarying > structure. Because I continually add such references, I don't want to > end up with docs that are hundreds of thousands of bytes. So, I want > to automate that when the number referenced in a given doc reaches a > certain point, say 20, that the doc selects only the newest (or most > recently added) and displays them, with a second generated page to > click to the next 20, etc. I could do that in MySQL, but LDAP seems > like the more logical choice, since, once entered, the data will not > be changed. > I really don't get what this has to do with LDAP authentication? Are you going to store the documents themselves in LDAP? Usually a documentation repository will use LDAP accounts and LDAP groups/roles to control access to content from the repository. I think LDAP itself would make a pretty lousy documentation repository.
> --- You are currently subscribed to ldap@umich.edu as: [EMAIL PROTECTED] To unsubscribe send email to [EMAIL PROTECTED] with the word UNSUBSCRIBE as the SUBJECT of the message.
