Linked by David Adams on Mon 20th Jul 2009 23:13 UTC
Permalink for comment 374415
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 06/17/13 17:58 UTC
Linked by Thom Holwerda on 06/17/13 17:52 UTC
Linked by Thom Holwerda on 06/14/13 21:03 UTC
Linked by Thom Holwerda on 06/14/13 20:46 UTC
Linked by Thom Holwerda on 06/14/13 17:32 UTC
Linked by Thom Holwerda on 06/14/13 11:39 UTC
Linked by Thom Holwerda on 06/14/13 11:32 UTC
Linked by Thom Holwerda on 06/13/13 19:39 UTC
Linked by Thom Holwerda on 06/13/13 14:45 UTC
Linked by Thom Holwerda on 06/13/13 11:43 UTC
More News »
Sponsored Links



Member since:
2006-12-21
PmWiki is filesystem based. So, it's as fast and as flexible as your filesystem. Also, unlike most that are based upon databases, PmWiki can take a slashdotting. Most db based wiki's fail because most people are not DBAs and do not have a scalable db infrastructure that can take the punishment.
PmWiki has a fantastic community, it is well designed, easy to extend and use. You can pretty much make it do anything you need it to do. With that said, many are NOT looking for a flexible platform, but something that has lots of fancy looking toys (because people in general stink at creating actual content). I would argue that PmWiki is a wiki for people that generate content and are not afraid to extend it on their own.
PmWiki runs our site intranet portal. In our case authentication is used and done against multiple sources including AD.
When we have a need for a new feature, I write the feature and also put the extension up on pmwiki's website for others to use as well. But we do have some extensions that are designed just to work with internal systems. We love it.