It seems like we're talking about different things...

I don't *care* if the page of the example expires... that's fine by me. It's the source code windows that keep expiring and really don't need to!

There bookmarkable page links could be used instead of ajax links IMHO. I don't care if the update refreshes the entire contents of the window instead of only the part with the source code in it... I *do* care if I look at the source code of a file for one of the examples for a few minutes that I can't look at another file without having to do the whole navigation again because the page keeps expiring...

Regards,
Sebastiaan

Martijn Dashorst wrote:
And it wouldn't guide our users into the right direction either: only
apply stateless pages where really necessary.

Martijn

On 3/18/08, Matej Knopp <[EMAIL PROTECTED]> wrote:
Not everything in wicket can be bookmarkable and not everything can be
 statelesss. None of the ajax examples could work on stateless pages
 for example.

 -Matej

 On Tue, Mar 18, 2008 at 10:52 AM, Sebastiaan van Erk

<[EMAIL PROTECTED]> wrote:
 > Matej Knopp wrote:
 >  > Why can't we just put a 5 minute timer on each page which would casuse
 >  > active sessions never expire?
 >
 >  That's fine by me, :-) though I tend to leave windows open in my browser
 >  for hours or days even, so that would be less server friendly than
 >  bookmarkable links...
 >
 >  Regards,
 >  Sebastiaan
 >
 >
 >
 >  > -Matej
 >  >
 >  > On Tue, Mar 18, 2008 at 8:52 AM, Sebastiaan van Erk <[EMAIL PROTECTED]> 
wrote:
 >  >> Martijn Dashorst wrote:
 >  >>  > Making the source code viewing pages stateless won't help: next
 >  >>  > question: but when I close the source code, my page doesn't work
 >  >>  > anymore.
 >  >>
 >  >>  The source code opens up in separate window. If the URL's there were
 >  >>  bookmarkable pages they would always work. Since the source is in a
 >  >>  separate window you can study the source code there and if the example
 >  >>  page expires, that's ok... Just refresh it.
 >  >>
 >  >>  I see no reason why the source code browser links should not be
 >  >>  bookmarkable; the reason they're not now is because they're ajax links,
 >  >>  and I'd prefer bookmarkable over ajax any day.
 >  >>
 >  >>  Regards,
 >  >>  Sebastiaan
 >  >>
 >  >>
 >  >>
 >  >>  > The online examples are not fit for a long studying session: they are
 >  >>  > for demoing, or visitors. Studying or long running demoes: DOWNLOAD
 >  >>  > the thing and run them locally.
 >  >>  >
 >  >>  >
 >  >>  > Martijn
 >  >>  >
 >  >>  > On 3/18/08, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
 >  >>  >> i think they meant to make only source code viewing pages 
stateless...
 >  >>  >>
 >  >>  >>
 >  >>  >>  -igor
 >  >>  >>
 >  >>  >>
 >  >>  >>
 >  >>  >>  On Tue, Mar 18, 2008 at 12:26 AM, Martijn Dashorst
 >  >>  >>  <[EMAIL PROTECTED]> wrote:
 >  >>  >>  > -1
 >  >>  >>  >
 >  >>  >>  >  You can download and run the examples yourself if you want to do 
so.
 >  >>  >>  >  The examples are just that: examples of normal wicket pages. 
Forcing
 >  >>  >>  >  them stateless gives new users the wrong impressions.
 >  >>  >>  >
 >  >>  >>  >  Martijn
 >  >>  >>  >
 >  >>  >>  >
 >  >>  >>  >
 >  >>  >>  >  On 3/18/08, Ned Collyer <[EMAIL PROTECTED]> wrote:
 >  >>  >>  >  >
 >  >>  >>  >  >  Hi,
 >  >>  >>  >  >
 >  >>  >>  >  >  I enjoy clicking around the source at 
http://www.wicketstuff.org/wicket13/.
 >  >>  >>  >  >  It's interesting stuff :)
 >  >>  >>  >  >
 >  >>  >>  >  >  Page expiry is very frustrating, especially when you tab back 
to the code to
 >  >>  >>  >  >  see how something is achieved.
 >  >>  >>  >  >
 >  >>  >>  >  >  Can we make the code pages either static or stateless, so I 
can bookmark
 >  >>  >>  >  >  them, send them to colleagues, or  come back 30mins later and 
click a link
 >  >>  >>  >  >  without it saying "page expired"?
 >  >>  >>  >  >
 >  >>  >>  >  >  Rgds
 >  >>  >>  >  >
 >  >>  >>  >  >  Ned
 >  >>  >>  >  >
 >  >>  >>  >  > --
 >  >>  >>  >  >  View this message in context: 
http://www.nabble.com/Wicketstuff-source-pages---can-we-make-them-stateless--tp16111827p16111827.html
 >  >>  >>  >  >  Sent from the Wicket - User mailing list archive at 
Nabble.com.
 >  >>  >>  >  >
 >  >>  >>  >  >
 >  >>  >>  >  >  
---------------------------------------------------------------------
 >  >>  >>  >  >  To unsubscribe, e-mail: [EMAIL PROTECTED]
 >  >>  >>  >  >  For additional commands, e-mail: [EMAIL PROTECTED]
 >  >>  >>  >  >
 >  >>  >>  >  >
 >  >>  >>  >
 >  >>  >>  >
 >  >>  >>  >  --
 >  >>  >>  >  Buy Wicket in Action: http://manning.com/dashorst
 >  >>  >>  >  Apache Wicket 1.3.2 is released
 >  >>  >>  >  Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.2
 >  >>  >>  >
 >  >>  >>  >
 >  >>  >>  >
 >  >>  >>  >  
---------------------------------------------------------------------
 >  >>  >>  >  To unsubscribe, e-mail: [EMAIL PROTECTED]
 >  >>  >>  >  For additional commands, e-mail: [EMAIL PROTECTED]
 >  >>  >>  >
 >  >>  >>  >
 >  >>  >>
 >  >>  >>  
---------------------------------------------------------------------
 >  >>  >>  To unsubscribe, e-mail: [EMAIL PROTECTED]
 >  >>  >>  For additional commands, e-mail: [EMAIL PROTECTED]
 >  >>  >>
 >  >>  >>
 >  >>  >
 >  >>  >
 >  >>
 >  >
 >  >
 >  >
 >




--
 Resizable and reorderable grid components.

http://www.inmethod.com


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




Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to