I just wanted to let you know that I have moved all the active
GrinnellPlans code to http://code.google.com/p/grinnellplans/ . Soon
we will have all the old bugs as well. The Google Code SVN repository
includes Ian Young's efforts to make Plans XHTML compatible.
Another big change that is live as of today on the server (and is of
course in the SVN):
** _SESSION ** changed! Instead of saving the session information on a
file on the server (the default PHP behavior) we now store them in the
cookie, encrypted (to ensure no one tampers with it). This means,
faster (less disk IO involved) and also, we can, ideally, swap web
servers without any user-noticeable disruption since all their session
metadata is stored in the cookie.
To use sessions one _must_ include cookie_session.php . I will be very
careful with what is included in the SVN—no passwords, no SQL dumps,
no weird random stuff.
Also, people who have access to the production server: changes made
directly in the server code (except Configuration.php) WILL be lost.
Ian.
Ian
In general, I don't see the logic in moving the session data to the
user-agent; we only _need to_ maintain user id in the cookie, so we're
not talking about a lot to pull from the database. Why can't we go
back to cookies holding session identifiers, and the real data living
on the server? I don't see that increasing server disk I/O or even
improving the user experience.
Avram