comment on

1. So CAP::Sessions won't complain about invoking session_config twice because I'm using the specific SESSION_NAME's?

That's the idea, yeah. Also make sure you pass a different -name to the COOKIE_PARAMS for each. If you do that, then both cookies will be set, as long as you do both calls to session_config.

2. How do I implement/install the patch on my server? (sorry, I'm not sure how all this works yet)

I don't recommend you use it for anything important since it's completely untested and I wrote it in a BBQ-induced stupor around 3AM. But if you really want to try it, download the CAP::Session tarball from CPAN, unpack it, and patch the files with the .diff attached to the RT ticket. Then use the Build.PL script as usual to build it. You might want to specify a prefix to install the module somewhere else so it doesn't overwrite your "real" install of CAP::Session.

In reply to Re^2: Is it possible to have 2 CAP::Sessions? by friedo
in thread Is it possible to have 2 CAP::Sessions? by bradcathey

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Perl: the Markov chain saw
	PerlMonks