Could you please expand on
"and you do not want to make custom logic to allow multi
window/tab (in browser)" ?

How exactly Wicket prevents the "multi browser tabs/windows" ?

Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov

On Wed, Dec 7, 2016 at 1:37 PM, Martin Makundi <
martin.maku...@koodaripalvelut.com> wrote:

> If one makes a single-page application that has multiple tabs (within one
> browser window), and you do not want to make custom logic to allow multi
> window/tab (in browser) management into session, it would work best if
> there was separate "session" for each browser tab/window inside wicket.
>
> Simplest example is that session has variable "currentlySelectedTab" if you
> have two browser windows open both will be racing for this same variable
> unless sessions are separated.
>
> So from developer's perspective, would be simplest if wicket transparently
> separates sessions for each browser window/tab.
>
> **
> Martin
>
>
>
> 2016-12-07 14:19 GMT+02:00 Martin Grigorov <mgrigo...@apache.org>:
>
> > Hi,
> >
> > What kind of problem exactly you try to solve there ?
> > What kind of issues do you face ?
> >
> > Martin Grigorov
> > Wicket Training and Consulting
> > https://twitter.com/mtgrigorov
> >
> > On Wed, Dec 7, 2016 at 12:07 PM, Martin Makundi <
> > martin.maku...@koodaripalvelut.com> wrote:
> >
> > > This should be built into wicket core, automatic session management.
> > Login
> > > once and enable multiple tabs and a new sub-session for each tab.
> > >
> > > If user logs out from any of the sessions, all would be invalidated.
> > >
> > > Not sure if this exists yet, but would be needed.
> > >
> > > **
> > > Martin
> > >
> > > 2016-12-07 12:59 GMT+02:00 Urbani, Edmund <edmund.urb...@lilandit.com
> >:
> > >
> > > > Ok, but how do you create a session per tab? Also, I would at least
> > need
> > > > to login the authenticated user in the new session.
> > > >
> > > >
> > > > On 12/07/2016 11:43 AM, Martin Makundi wrote:
> > > >
> > > > We have noticed that most robust if you can get different session for
> > > each
> > > > tab because the session shares models and will easily conflict if
> > session
> > > > is not distinct for each tab.
> > > >
> > > >
> > > >
> > > > 2016-12-07 12:42 GMT+02:00 Urbani, Edmund <
> edmund.urb...@lilandit.com>
> > <
> > > edmund.urb...@lilandit.com>:
> > > >
> > > >
> > > > Hi all,
> > > >
> > > > I have a some questions about the current state of this feature.
> > > >
> > > > Firstly, how reliable is it? (Works on all/current browsers? Can
> still
> > > > break under certain circumstances?)
> > > >
> > > > And secondly, how would I store my own state information per
> > tab/window?
> > > > The session context seems too broad because it is shared by all tabs
> > and
> > > > the page context is too limited.
> > > >
> > > > I could make it work with the session anyway, if I can somehow
> identify
> > > > the current browser tab and put things into a map accordingly. Or I
> > could
> > > > pass on all required info from page to page which would be quite
> > > cumbersome
> > > > and conflict with my approach to use bookmarkable URLs wherever
> > possible.
> > > >
> > > > Kind regards,
> > > >  Edmund
> > > >
> > > >
> > > > ------------------------------------------------------------
> ---------
> > > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> > > > For additional commands, e-mail: users-h...@wicket.apache.org
> > > >
> > > >
> > > >
> > > > --
> > > >
> > > > Edmund Urbani
> > > > Liland IT Team
> > > >
> > > > Email: edmund.urb...@lilandit.com <edmund.urb...@lilandit.com>
> > > >
> > > > Liland IT GmbH ...does IT better
> > > > Tel: +43 463 220111
> > > > Fax: +43 463 220111-33
> > > > Tel(GER): +49 221 65028588
> > > >
> > > > Find us at Facebook http://facebook.com/Lilandit
> > > > http://iventcloud.com
> > > > http://Lilandit.com
> > > >
> > > > <http://www.LilandIT.com> <http://www.LilandIT.com>
> > > >
> > > > Copyright © 2016, Liland IT GmbH
> > > >
> > > > Diese Mail enthaelt vertrauliche und/oder rechtlich geschuetzte
> > > > Informationen.
> > > > Wenn Sie nicht der richtige Adressat sind oder diese Email
> irrtuemlich
> > > > erhalten haben, informieren Sie bitte sofort den Absender und
> > vernichten
> > > > Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte
> Weitergabe
> > > > dieser Mail ist nicht gestattet.
> > > >
> > > > This email may contain confidential and/or privileged information.
> > > > If you are not the intended recipient (or have received this email in
> > > > error) please notify the sender immediately and destroy this email.
> Any
> > > > unauthorised copying, disclosure or distribution of the material in
> > this
> > > > email is strictly forbidden.
> > > >
> > >
> >
>

Reply via email to