On Jan 21, 2008 4:31 PM,  <[EMAIL PROTECTED]> wrote:
> Thanks. I looked that source of the staticpages examples and even more 
> troubled with it. It generates each static links via a costly
> markup object creation and attribute modification.
> In a base template page that may contain,say 50 such links,
> that would be displayed for all site (bookmarkable) pages,
> it would mean  a lot of object creation/destruction just for a static markup.

have you profiled how expensive creating these objects really is? i
would be curious about the numbers you get.

>I saw a post about running out of wicket memory during stress test.

was that because there was a memory leak in wicket code or in the user's code?

>I had quite a few times  >noticing the turnaround is quite slow in my
app even though it is just a page with many >constructed links, even
though I do not have test suite to back it up.

have you tried starting your app in deployment mode? development mode
has quiet a lot of overhead which gets you better error reporting.

> Would it be possible to turn a bookmarkale/stateless page object
> into a stateful page during a session once user first access it.

these pages are not created until accessed...so not sure what you mean

> After all, bookmarkable page link is for accessing the page when you
> return to it after ,say  a few days. Once you access/create it,
> during the session, it should be considered a stateful.

yes and it is, however, it is up to you to determine the scope that
defines its statefulnes. you do  this like you do with most other java
objects - by holding onto its reference.

for conversation scopes you pass the reference around into pages that
define the conversation

for session scope you should store that reference within session.

> >>  This is obviouly a huge performance issue.

really? maybe to make it obvious you should show some numbers so we
can compare. maybe a graph...personally i love pie charts :)

-igor

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to