amazon is also a very simple site if i may say
the webshop are a few pages at most ...
Also they have a lot of cookies called "session" something...
And i didnt see much change in the cookies when i added something to my card
but it could be encoded in one of them i guess.
But removing some cooki
i agree with a lot of what eelco says here. that said, i'm definitely more
of the mind to prefer stateful OO techniques over stateless. also, i think
the idea that amazon is actually a stateless web site is probably somewhat
false already and getting more false as the company grows and scales t
Eelco,
Thanks for the thorough and thoughtful reply. Perhaps there are things that
can be done in the framework with cookies and such.
I am going to be looking to additions to wicket. I need to get the source
built and working in my local environment.
-Doug
Eelco Hillenius wrote:
>
>
>>
Hi,
See reaction inline.
> Stateless Sites
> -
>
> For example, Google's search is apparently stateless. I can bookmark any
> search result, go away for hours, days or weeks and re-visit the link
> without experiencing a session-expired message. I shop at Amazon quite a
>
here are my two cents on this:
wicket is optimized to scale well when building web application with
complex user interfaces. all the examples you gave: amazon, google
search, are web sites, not web applications: they have few pages with
simple user interfaces. so if whatever it is you are building
that's probably because the session timeout on the container hosting that
example is short.
Doug Donohoe wrote:
>
> I'm using Wicket 1.3.3 on Tomcat 6.0.16. I'm using whatever the default
> session store implementation is because I haven't done anything to
> configure it.
>
> Are you suggest
I'm using Wicket 1.3.3 on Tomcat 6.0.16. I'm using whatever the default
session store implementation is because I haven't done anything to configure
it.
Are you suggesting there is a way to avoid session expirations?
I'm not sure your previous suggestion to lengthen session time-out solves
th
the more i think about this, the more i'm suspecting you've just got a bunch
of configuration problems.
what version of wicket are you using and what session store implementation?
also, tomcat provides a facility for writing out less active sessions to
disk.
Doug Donohoe wrote:
>
> Hi Jonath
there may be places where improvements are possible, but i think the answer
is not to ruin your programming model by not using sessions. i think
bookmarkability is a separate issue and one that is quite nicely addressed
in wicket /when you need it/.
one simple thing you can do to increase your
the examples app are just bad example because there the session expiration
is 5 minutes or something like that
You can up the session expiration to 24 hours or something like that then it
wont happen at all
If you want or use ajax and wicket then you can forget about being stateless
because that
Hi Jonathan,
I'd like to open a discussion about this stance on "stateless" web ui
because I think the original question is really one about Wicket's use of
the session. By default, all wicket forms and links are stateful or
dependent on the Wicket Session. If the session goes away, the links a
11 matches
Mail list logo
