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.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||