Sorry for jumping into this issue again, but I am still a bit confused. I
need a definitive answer for this as I have to document it in my diploma
thesis.
In my app I have a requirement that a new page has to be opened in a popup
window, which is pretty easy with wicket using the popupsettings o
et="_blank" and physically opening a
new window using the browser can get different results.
-Original Message-
From: Igor Vaynberg [mailto:igor.vaynb...@gmail.com]
Sent: Sunday, July 26, 2009 2:50 PM
To: users@wicket.apache.org
Subject: Re: Questions about Wicket sessions
On Su
>> So if I dont use clustered web servers, custom methods on a custom session
>> object do not need be "synchronized". Put it another way, Wicket session is
>> thread-safe in case of a single web server. Correct?
>>
>> Cheers.
>>
>>
>> --- On Sun,
Igor Vaynberg wrote:
2. If I start IE or FF in another window, visitor activities on the same Wicket
app are considered in the same or different session?
always a different sessions, browsers do not share sessions.
I think it depends on what David meant by 'another window'. I assumed
Igor, thank you for the correction. Really appreciated. Thanks!
--- On Sun, 7/26/09, Igor Vaynberg wrote:
> From: Igor Vaynberg
> Subject: Re: Questions about Wicket sessions
> To: users@wicket.apache.org
> Date: Sunday, July 26, 2009, 4:23 PM
> no, incorrect. multiple browse
ustom methods on a custom session
> object do not need be "synchronized". Put it another way, Wicket session is
> thread-safe in case of a single web server. Correct?
>
> Cheers.
>
>
> --- On Sun, 7/26/09, Erik van Oosten wrote:
>
>> From: Erik van Oosten
>&
an Oosten wrote:
> From: Erik van Oosten
> Subject: Re: Questions about Wicket sessions
> To: users@wicket.apache.org
> Date: Sunday, July 26, 2009, 2:08 PM
> David,
>
> Please note "Sessions are not thread-safe" in Wicket
> context means that the Session /object
On Sun, Jul 26, 2009 at 8:53 AM, David Chang wrote:
> 1. If I open another tab on the same browser (IE or FF), visitor activities
> on the same Wicket app are considered in the same session?
same session, this is why we provide browser auto-multiwindow support,
so we can detect a new tab/window b
David,
Please note "Sessions are not thread-safe" in Wicket context means that
the Session /object/ is not thread-safe. Note that requests that fall
within a session (except for resources) are handled serially. Only when
you use session clustering this guarantee can not be made.
1. It depend
Chang wrote:
> From: David Chang
> Subject: Questions about Wicket sessions
> To: users@wicket.apache.org
> Date: Sunday, July 26, 2009, 11:53 AM
>
>
>
> Reading <> to learn Wicket, I
> understand that sessions are not thread-safe. I have the
> following questi
Reading <> to learn Wicket, I understand that sessions are
not thread-safe. I have the following questions about a Wicket app:
1. If I open another tab on the same browser (IE or FF), visitor activities on
the same Wicket app are considered in the same session?
2. If I start IE or FF in anot
11 matches
Mail list logo