There are LDAP plugins to AccountManager that will allow tracd to authenticate against LDAP, so that's not really a reason.
Other than probable performance (though tracd isn't that much of a slouch), the reason I see to not use ti directly are: * Based on the Python HTTP server. While not necessarily a bad thing, I bet apache/lighttpd/nginx have been pounded on more from an HTTP perspective than the Python HTTP server. * Can't do SSL. This is a big one if you don't want to be sending passwords in plain text. Now, that being said, my preferred setup for trac is actually running multiple tracd instances behind an nginx proxy. This gives me a robust HTTP server, the ability to do SSL and the ease of tracd. -John --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
