Wicket Session Management?

[Pen <du...@yahoo.com>]

I have a few question regarding the wicket usage. we are trying to Implement
wicket as our next MVC framework, Can please someone answer the questions
below

- about session support - wicket stores the render state of most renderer's
in session for different users of the systems. This means large/very large
sessions that need to be supported, means memory crunch, performance
degradation and implementing the failover at production level really hard.

- Also it looks like wicket  requires code changes when more pages are added
and each page needs to have separate handler and it can not be done in
configuration file. This may become an issue when number of pages increase
in future.

Dummy


-- 
View this message in context: http://www.nabble.com/Wicket-Session-Management--tf4721575.html#a13498748
Sent from the Wicket - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org

Re: Wicket Session Management?

[Pen <du...@yahoo.com>]

Thanks Matej for your quick reply, these are stupid questions asked by the
team members, who are resisting to implement Wicket. Trying to come up with
some issues.

So basically you are telling that session management is not a issue at all
in wicket, that's good.


Thanks Again!

Dummy


Matej Knopp-2 wrote:
> 
> Pen  wrote / napísal(a):
>> I have a few question regarding the wicket usage. we are trying to
>> Implement
>> wicket as our next MVC framework, Can please someone answer the questions
>> below
> 
> Hi
>> 
>> - about session support - wicket stores the render state of most
>> renderer's
>> in session for different users of the systems. This means large/very
>> large
>> sessions that need to be supported, means memory crunch, performance
>> degradation and implementing the failover at production level really
>> hard.
> Wicket doesn't store a render state of renderer's (have no clue what 
> that might be). Wicket stores a component tree of last page in session.
> 
> Btw. this doesn't even sound like a question, it sounds like stating 
> facts, not to mention that the facts are based on wrong assumtptions.
> 
> Very large sessions? I've seen a model 2 application with sessions over 
> a megabyte. Usually a wicket page is (unless it's a big one - with lot 
> of components) around 30kb (of course this is very relative, this just 
> reflects my experience with most of my wicket based projects). I don't 
> think a 30kb session results in performance degradation or makes 
> implementing failover difficult.
> 
>> 
>> - Also it looks like wicket  requires code changes when more pages are
>> added
>> and each page needs to have separate handler and it can not be done in
>> configuration file. This may become an issue when number of pages
>> increase
>> in future.
>> 
> 
> What handler? What configuration file? Page has a class that implements 
> the logic (probably what you mean by "handler"). How is this related to 
> a config file? Wicket doesn't need any config file. There's no external 
> plumbing. I fail to see how this results in an issue with increased page 
> numbers, as the pages are completely independent.
> 
> Also I'm kinda missing a question mark in this question again, which 
> make it seem like a statement (wrong again as far as I can tell). I'm 
> not sure if that was intended.
> 
> -Matej
> 
>> Dummy
>> 
>> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/Wicket-Session-Management--tf4721575.html#a13500318
Sent from the Wicket - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org

Re: Wicket Session Management?

[Matej Knopp <ma...@gmail.com>]

Pen  wrote / napísal(a):
> I have a few question regarding the wicket usage. we are trying to Implement
> wicket as our next MVC framework, Can please someone answer the questions
> below

Hi
> 
> - about session support - wicket stores the render state of most renderer's
> in session for different users of the systems. This means large/very large
> sessions that need to be supported, means memory crunch, performance
> degradation and implementing the failover at production level really hard.
Wicket doesn't store a render state of renderer's (have no clue what 
that might be). Wicket stores a component tree of last page in session.

Btw. this doesn't even sound like a question, it sounds like stating 
facts, not to mention that the facts are based on wrong assumtptions.

Very large sessions? I've seen a model 2 application with sessions over 
a megabyte. Usually a wicket page is (unless it's a big one - with lot 
of components) around 30kb (of course this is very relative, this just 
reflects my experience with most of my wicket based projects). I don't 
think a 30kb session results in performance degradation or makes 
implementing failover difficult.

> 
> - Also it looks like wicket  requires code changes when more pages are added
> and each page needs to have separate handler and it can not be done in
> configuration file. This may become an issue when number of pages increase
> in future.
> 

What handler? What configuration file? Page has a class that implements 
the logic (probably what you mean by "handler"). How is this related to 
a config file? Wicket doesn't need any config file. There's no external 
plumbing. I fail to see how this results in an issue with increased page 
numbers, as the pages are completely independent.

Also I'm kinda missing a question mark in this question again, which 
make it seem like a statement (wrong again as far as I can tell). I'm 
not sure if that was intended.

-Matej

> Dummy
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org

Re: Wicket Session Management?

[Johan Compagner <jc...@gmail.com>]

>
>
> - Also it looks like wicket  requires code changes when more pages are
> added
> and each page needs to have separate handler and it can not be done in
> configuration file. This may become an issue when number of pages increase
> in future.



what do you mean with this? You want to have the flow between pages in a xml
file?
Please explain to me how you want to do that exactly, i am always very
curious why
the web frameworks all really want this.

How do you see that you can just drop in a new page. And then configure an
xml file
and that page is suddenly the response page of 5 other pages (actions) ?
But what state does that new page get? Are all the pages that you show
completely stateless
they can construct themself from something and know what they must show and
what there context is?

So how do all the previous pages know exactly what context to set somewhere
that the new page wants?

Please if anybody could tell me how they can build an application with flow
where all the pages
don't really know anything of the next page of even what the next page
really is.

Is there 1 person on this list that made a struts or webflow application
like this that they can randomly
define flow and add pages without touching the existing code base?

johan