pp wrote: > Not especially. Just notice that as a user You log to admin interface once. > And midgard authentication lets You keep information about who is logged.
No, it's resent by the browser in every request. Every page request that requires authentication does all the work all over again. That's how HTTP authentication works. > Whatever You do , You are always objects creator. Right? > So midgard authentication system could store also user username. Well, we could... but down that path madness lies. Once you start de-normalizing your tables... > And imagine site where You need fetch 500-1000 articles , and get every > person for every article. Next 500-1000 querries are needed then for getting > person username. > > Got an idea? Yes, but the same argument could be made for any other linked resource. The database server should cache and index to make this efficient enough. Or we could add it to the query, which would need a join, but then again: where does it stop? The title of the parent topic for an article? Or the full path of titles of parent topics? Group name for a person? Etc. > Yeeeeeees.... I just noticed ;) > But We are talking about users who log to any midgard sites. > They _need_ username. You mean just the currently logged-on user? OK, that's reasonable. Emile --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
