Think that it might be beneficial to make a list of things we intend to improve/fix, and then see if people are interested in taking a particular piece? Here is my personal list, covering both branches:
- Improving test coverage - Fix documentation inconsitencies (there are a few) - Fix session expiration, or verify that session expiration is now working - Verify compatibility with CGI::Simple and CGI::Safe - Inconsistent driver interfaces - Asinine requirement that all drivers must be lowercase (WTF? ;)There's likely more, but I'm too sleep deprived to think of them right now ;)
Jason Mark Stosberg wrote:
For those just tuning in: A group of CGI::App users have decided to 'phalanx' CGI::Session, which is to say we have taken it upon ourselves to improve it. To that end, one or more source control repos will be setup to faciliate groupdevelopment.I have just contacted the author and await his response about how to best collaborate with him. (However, we don't need to wait on hisresponse to continue setting up our infrastructure).I have also just reviewed what's new in the 4.x branch, which I'll repeat below. In summary, I think these are generally the kinds of things we would end up adding ourselves if we started with the 3.x branch as a base. Therefore, (contradicting what I've said before), I think the 4.x branch should be our primary development branch. I do however think our first order of business should be confirming compatibility with the 3.x branch, which I knowmany of us care about it.That should not be a hard project to get started on-- we can simply copy over thetests from the 3.x test suite as a starting point.Another good first-stage task would be to run Devel::Cover on the project andsee where there are tests missing.I know Jason is in the process of graciously setting up an SVN server for us. I may also go ahead and set up a darcs repo soon too, realizing that we can use'tailor.py' to provide a two-way sync so that both are useful.Finally, if there are concerns that this side-project will generate two much noise on this list, we can take the conversation elsewhere, such asthe CGI::Sessions user list (which seems to be unfortunately quiet).Mark 4.00_08 - Tuesday, March 15, 2005 * FIX: Changes made in 4.00_07 rolled back 4.00_07 - Sunday, March 13, 2005 * FIX: overloaded objects are now stored properly 4.00_06 - Thursday, February 24, 2005 * FIX (?): a test script was failing on Win32 * FIX: inaccurate error reporting in load() 4.00_05 - Tuesday, February 22, 2005 * FIX: case insesitivity was not enforced properly in CGI::Session::parse_dsn() 4.00_04 - Wednesday, February 16, 2005 * FIX: Minor fix in tests suits and error-checking routines of serializers and id-generators 4.00_03 - Friday, February 11, 2005 * NEW: CGI::Session::find() introduced * NEW: traverse() introduced into drivers to support CGI::Session::find() * DOCS: More complete driver specs documented 4.00_02 - Wednesday, February 09, 2005 * FIX: race conditions in Driver/file.pm pointed out by Martin Bartosch 4.00_01 - Wednesday, February 09, 2005 * NEW: load() - constructor method to prevent unnecessary session creations * NEW: is_expired() - method to intercept expired sessions * NEW: is_empty() - to intercept requests for unexisting sessions * NEW: more optimized source code * NEW: updated and improved driver specs * NEW: standard testing framework * NEW: 'sqlite' driver
---------------------------------------------------------------------
Web Archive: http://www.mail-archive.com/suppressed/
http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: suppressed
For additional commands, e-mail: suppressed
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.