From: Wesley M. <we...@we...> - 2003-09-15 22:58:40
|
Hi Chad, > Wesley has been submitting some good bugs and patches. I greatly > appreciate it. If you interested, I can get you CVS access to fix your > own bugs and perhaps you can explain to the list a bit more on your > username/password implementation. If you have it up that we can see it > that would be great as well. Sure. CVS access would be great. Thanks. :) I'll describe a little bit of how the username/password system works. If you want to see it, you can go to http://www.wesman.net/~wesley/ical/ I don't really have a username and password for you to try it out with, since this is my personal calendar setup. But basically when you log in the login box goes away and is replaced with a Logout <username> link below the navigation links on the sidebar. What happens is a map of username:password pairs are associated with an array of calendar names in the config.inc.php file. Then, the subroutine that normally handles the loading of a single calendar or multiview calendars checks if there is a username and password either from GET, POST, or cookie (GET and POST override cookies) for calendars the user can access. This list of accessible calendars is equal to (all calendars - blacklisted - locked + unlocked). Logging out deletes the cookies and reloads the current HTTP request with the username and password removed from the query string if it exists. The patch I submitted uses GET to login; I changed it to POST later on but after I submitted the patch. Hope that answers some questions. Ask me more questions, criticize, etc. Later, -- Wesley Miaw, Wesley Miaw Consulting http://www.wesman.net/ -- Wesley Miaw we...@cs... |