wrote:
On Mon, 2009-03-09 at 13:07 +0100, Martijn Dashorst wrote:
Starts to sound like a form of premature optimization. If you are
new
to Wicket, why do you want to implement a memcached session store?
What is the usecase?
We're starting a new project
On Mar 9, 2009, at 7:03 AM, Martin Grotzke wrote:
On Mon, 2009-03-09 at 13:07 +0100, Martijn Dashorst wrote:
Starts to sound like a form of premature optimization. If you
are new
to Wicket, why do you want to implement a memcached session
store?
What is the usecase?
We're
wrote:
Starts to sound like a form of premature optimization. If you
are
new
to Wicket, why do you want to implement a memcached session
store?
What is the usecase?
We're starting a new project (the relaunch of a big ecommerce
system)
and want to be able
to Wicket, why do you want to implement a memcached session
store?
What is the usecase?
We're starting a new project (the relaunch of a big ecommerce
system)
and want to be able to scale out (just throw in new hardware when
traffic grows). Additionally we have the requirement of session
are
new
to Wicket, why do you want to implement a memcached session
store?
What is the usecase?
We're starting a new project (the relaunch of a big ecommerce
system)
and want to be able to scale out (just throw in new hardware
when
traffic grows). Additionally we have the requirement of session
to Wicket, why do you want to implement a memcached session store?
What is the usecase?
We're starting a new project (the relaunch of a big ecommerce
system)
and want to be able to scale out (just throw in new hardware when
traffic grows). Additionally we have the requirement of session
failover
Just to be complete, even if this is not really an option for us: with
ONE_PASS_RENDER clustering with wicket would be fine, no further state
management issues, right?
Right. And there is back button support (access to older pages/
previous renderings) to consider, which without session
to Wicket, why do you want to implement a memcached session store?
What is the usecase?
We're starting a new project (the relaunch of a big ecommerce system)
and want to be able to scale out (just throw in new hardware when
traffic grows). Additionally we have the requirement of session
On Wed, 2009-03-11 at 09:31 -0700, Eelco Hillenius wrote:
Just to be complete, even if this is not really an option for us: with
ONE_PASS_RENDER clustering with wicket would be fine, no further state
management issues, right?
Right. And there is back button support (access to older
:
Starts to sound like a form of premature optimization. If you are new
to Wicket, why do you want to implement a memcached session store?
What is the usecase?
We're starting a new project (the relaunch of a big ecommerce system)
and want to be able to scale out (just throw in new
:
On Mon, 2009-03-09 at 13:07 +0100, Martijn Dashorst wrote:
Starts to sound like a form of premature optimization. If you are
new
to Wicket, why do you want to implement a memcached session store?
What is the usecase?
We're starting a new project (the relaunch of a big ecommerce
;)
Cheers,
Martin
On Mar 9, 2009, at 7:03 AM, Martin Grotzke wrote:
On Mon, 2009-03-09 at 13:07 +0100, Martijn Dashorst wrote:
Starts to sound like a form of premature optimization. If you
are new
to Wicket, why do you want to implement a memcached session
store?
What is the usecase
Martijn
On Mon, Mar 9, 2009 at 3:03 PM, Martin Grotzke
martin.grot...@javakaffee.de wrote:
On Mon, 2009-03-09 at 13:07 +0100, Martijn Dashorst wrote:
Starts to sound like a form of premature optimization. If you are new
to Wicket, why do you want to implement a memcached session store
;)
Cheers,
Martin
On Mar 9, 2009, at 7:03 AM, Martin Grotzke wrote:
On Mon, 2009-03-09 at 13:07 +0100, Martijn Dashorst wrote:
Starts to sound like a form of premature optimization. If you are new
to Wicket, why do you want to implement a memcached session store?
What
Hi,
sounds interesting. What would you say are the advantages of terracotta
over memcached? I'd say in terms of scalability terracotty has the same
disadvantages like local (in-jvm) caches - replication has to be done to
all other nodes.
Thanx for your thoughts,
cheers,
Martin
On Sun,
On Sun, 2009-03-08 at 16:56 -0700, Victor Igumnov wrote:
I wrote a memcached session manager store for jetty, that our wicket
app utilizes. Works well, except I can't open source it,
since it was created on the company's dime ;-(
Well, most interesting things are not so simple to realize that
Starts to sound like a form of premature optimization. If you are new
to Wicket, why do you want to implement a memcached session store?
What is the usecase?
Martijn
On Mon, Mar 9, 2009 at 9:56 AM, Martin Grotzke
martin.grot...@javakaffee.de wrote:
On Sun, 2009-03-08 at 16:56 -0700, Victor
On Mon, 2009-03-09 at 13:07 +0100, Martijn Dashorst wrote:
Starts to sound like a form of premature optimization. If you are new
to Wicket, why do you want to implement a memcached session store?
What is the usecase?
We're starting a new project (the relaunch of a big ecommerce system)
and want
of premature optimization. If you are new
to Wicket, why do you want to implement a memcached session store?
What is the usecase?
We're starting a new project (the relaunch of a big ecommerce system)
and want to be able to scale out (just throw in new hardware when
traffic grows). Additionally we
.
On Mar 9, 2009, at 7:03 AM, Martin Grotzke wrote:
On Mon, 2009-03-09 at 13:07 +0100, Martijn Dashorst wrote:
Starts to sound like a form of premature optimization. If you are new
to Wicket, why do you want to implement a memcached session store?
What is the usecase?
We're starting a new project
Hi,
we're just thinking about a session store using memcached. I just want
to ask if somebody already implemented this (and wants to share) before
we implement this.
Btw, is there some documentation about ISessionStore semantics, in
addition to javadocs? I would be interested in the order in
You can check the TIM integration work from the Terracotta guys. That
should make things easier, and you could even try it out, perhaps
saving a memcached implementation completely :)
Martijn
On Sun, Mar 8, 2009 at 11:01 PM, Martin Grotzke
martin.grot...@javakaffee.de wrote:
Hi,
we're just
I wrote a memcached session manager store for jetty, that our wicket
app utilizes. Works well, except I can't open source it,
since it was created on the company's dime ;-(
Here is my opinion on memcached as a session store.
Memcached will not work well as a wicket session store, due to 1mb
23 matches
Mail list logo
