Re^2: Using CGI:App and Session plugin - double DB connection fix.

Exactly what I was thinking.

Yesterday I needed a way to get a list of all blocks inside config file (ini type) from Config::Simple, and I implemented it ... Will do that now with CGI::Session.

What's the standard procedure in cases like that? Just send an email to authors/maintainers saying what did you changed and attach the file?

Comment on Re^2: Using CGI:App and Session plugin - double DB connection fix.

Replies are listed 'Best First'.
Re^3: Using CGI:App and Session plugin - double DB connection fix. by cees (Curate) on Sep 15, 2005 at 12:54 UTC
If there is a mailing list for the module, sign up and send the info there. Usually module maintainers prefer to get changes in the form of a diff file (usually diff -u is the prefered format). If you don't use *nix, and don't have diff, then I'm sure you could send the entire file that you changed. Also, module maintainers are usually very happy if you include some new tests for the test suite that make sure your new feature is working properly. Before you go an do all that work though, it might be worthwhile bringing it up on the mailing list to see if the maintainer will be receptive to the change or not.	[reply]

Replies are listed 'Best First'.

Re^3: Using CGI:App and Session plugin - double DB connection fix.
by cees (Curate) on Sep 15, 2005 at 12:54 UTC

If there is a mailing list for the module, sign up and send the info there. Usually module maintainers prefer to get changes in the form of a diff file (usually diff -u is the prefered format). If you don't use *nix, and don't have diff, then I'm sure you could send the entire file that you changed.

Also, module maintainers are usually very happy if you include some new tests for the test suite that make sure your new feature is working properly.

Before you go an do all that work though, it might be worthwhile bringing it up on the mailing list to see if the maintainer will be receptive to the change or not.

[reply]