From: Jeff D. <da...@da...> - 2001-09-17 18:09:41
|
> Hmm. As a serialized string? You might want to expand on this. I think the > idea of them having a home page on the wiki is a natural. The new database API allows (more-or-less) for arbitrary key/value pairs to be attached to pages as meta-data. This data is accessed via the WikiDB_Page::get() and WikiDB_Page::set() methods. (And yes, the implementation involves storing a serialized hash.) So this is a real quick-and-dirty place to store user meta-data if we establish a correspondence between users and pages. I'm thinking that pages which serve as user homepages would have additional meta-data something like: is_homepage: 1 password: md5:12ef... user_email: <da...@da...> This is data that would otherwise be stored in a separate user database (e.g. /etc/passwd). > Like I said, it just seems like a natural. I would use SteveWainstead or > just 'wainstead' as an ID and would want my name to hyperlink to a page > about me. Yes, my main point of concern/confusion right now concerns the following scenario: You attempt to register (via some automatic scheme, like the one you've outlined below) as a new user with the userid SteveWainstead. The page SteveWainstead already exists. What to do? Should you be allowed to take over the existing page as your homepage? (What if you were trying to register under the userid of FrontPage or CategoryNextWiki?) (I guess this scenario addresses a more generic issue than that of just user registration --- more that of page ownership. Who should be allowed to own/lock which (pre-existing) pages?) > What I would really like to see added is user registration, where users > must have a valid email address to register with the Wiki. This would be > useful for a public wiki that only allows members to edit pages, and > guests can only browse. In corporate intranets this would be essential. Yes. This is what has been in the back of mind (I think you planted the seed there) for awhile now. I keep hoping to find some pre-written library which handles the details, but I don't think were going to find one... |