The app is constructed so that the user first encounters a login page where he can enter his username and password, and the name of the server he wants to work on, [...] I use (abuse?) Dancer2's session mechanism to store all the relevant data from the server the user working on - and here is my problem. Dancer2's sessions are, in effect, per browser.

Your problem is your login page. Dancer2's session's aren't per browser. They are per browser, server, and TCP port. If Dancer2 uses cookies for storing a session key (most likely it does), you can set the cookies for a subtree of the document tree. So if you construct your URLs to look like http://loginserver.example.com/session/littleserver/..., http://loginserver.example.com/session/bigserver/..., http://loginserver.example.com/session/otherserver/..., and so on, and set the cookies path to include the server name (i.e. /session/littleserver, /session/bigserver, ....), Dancer2 should not confuse the sessions.

Alexander

--
Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)

In reply to Re: Dancer2 per-window sessions? by afoken
in thread Dancer2 per-window sessions? by kikuchiyo

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • 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:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, 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, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.