On Thu, 2006-07-27 at 15:04 -0500, Lane, Ryan wrote:
Actually, I'd like to have a feature like this completed in the next couple of releases for the LDAP plugin. I'm looking for a way to do this that won't kill my LDAP servers. If LDAP is your authorization store, it *could* be getting hit every page view, and caching authorization usually isn't a good idea (the most I'd be comfortable with would be caching for sessions, with short sessions).
Does PHP do connection pooling with LDAP the same way it does connection pooling with SQL dbs? Seems that the hammering would occur if a new connection is initiated every time, but that things should be reasonably tame if it's treating it as a DB.
- Structured data - I know that in my last job, there were several
things we used a wiki in lieu of a database for (e.g. we kept a list
of
new licensees of our technology on a wiki). It was nice, because we
had
the flexibility to add fields willy-nilly. So, it may be interesting
to
discuss the enterprise applicability of projects like
I remember seeing a couple things that were interesting in regards to this. One is Semantic Mediawiki, and the other was the wiki database extension that was mentioned in the wikitech list. I think there is also a sortable table extension.
Argh...looks like I forgot to finish that sentence. Yes, I meant to namedrop both Semantic MediaWiki and Wikidata. I probably got distracted at the point I was going to search for any other stuff that might fit the bill.
Another extension that I think is very interesting for enterprise use is the stable version extension. This is a great way of avoiding part of the "we *need* ACLs" problem you can run into in enterprise environments.
Ah, right. I worked on something like that in my last gig. My understanding is that they plan to open source it, but I haven't seen anything on that yet.
You're right though. People will likely be more comfy without write acls if the only thing people can edit is a "draft" that's has to be approved before publication.
Rob