On Friday, 18 March 2011 at 20:18, tedd wrote:
At 8:03 PM + 3/18/11, Stuart Dallas wrote:
> > On Friday, 18 March 2011 at 19:56, tedd wrote:
> > At 7:26 PM + 3/18/11, Stuart Dallas wrote:
> > > > On Friday, 18 March 2011 at 19:14, tedd wrote:
> > > > At 3:53 PM + 3/18/11, Stuart Dallas
At 8:03 PM + 3/18/11, Stuart Dallas wrote:
On Friday, 18 March 2011 at 19:56, tedd wrote:
At 7:26 PM + 3/18/11, Stuart Dallas wrote:
> On Friday, 18 March 2011 at 19:14, tedd wrote:
> At 3:53 PM + 3/18/11, Stuart Dallas wrote:
> > > The cookies I use to replace sessions are sessio
On Friday, 18 March 2011 at 19:56, tedd wrote:
At 7:26 PM + 3/18/11, Stuart Dallas wrote:
> > On Friday, 18 March 2011 at 19:14, tedd wrote:
> > At 3:53 PM + 3/18/11, Stuart Dallas wrote:
> > > > The cookies I use to replace sessions are session-based cookies and
> > > > last no longer than
At 7:32 PM + 3/18/11, Stuart Dallas wrote:
On Friday, 18 March 2011 at 18:06, Nathan Nobbe wrote:
CI seemed to have a problem in that it would not spill data over
into additional cookies when the size of one cookie was maxed out.
One way to tell it's time to rethink your paradigm is when y
At 7:26 PM + 3/18/11, Stuart Dallas wrote:
On Friday, 18 March 2011 at 19:14, tedd wrote:
At 3:53 PM + 3/18/11, Stuart Dallas wrote:
> The cookies I use to replace sessions are session-based cookies and
> last no longer than a traditional PHP session. The key is to provide
> a lightwe
On Friday, 18 March 2011 at 18:06, Nathan Nobbe wrote:
> CI seemed to have a problem in that it would not spill data over into
> additional cookies when the size of one cookie was maxed out. One way to tell
> it's time to rethink your paradigm is when you're using up the maximum number
> of cook
On Friday, 18 March 2011 at 19:14, tedd wrote:
At 3:53 PM + 3/18/11, Stuart Dallas wrote:
> > The cookies I use to replace sessions are session-based cookies and
> > last no longer than a traditional PHP session. The key is to provide
> > a lightweight method of ensuring that whichever server
On Friday, 18 March 2011 at 19:25, Torsten Rosenberger wrote:
If i am right then you have 1.44KB per request ?
>
I've never done the analysis, but it's an AJAX-heavy site so that could well be
the average.
-Stuart
--
Stuart Dallas
3ft9 Ltd
http://3ft9.com/
> "Stuart Dallas" schrieb:
>
> >
If i am right then you have 1.44KB per request ?
BR/Torsten
"Stuart Dallas" schrieb:
>On Friday, 18 March 2011 at 17:36, Nathan Nobbe wrote:
>On Fri, Mar 18, 2011 at 11:19 AM, Stuart Dallas wrote:
>> > On Friday, 18 March 2011 at 17:14, Torsten Rosenberger wrote:
>> > > > I'm curious to know
At 3:53 PM + 3/18/11, Stuart Dallas wrote:
The cookies I use to replace sessions are session-based cookies and
last no longer than a traditional PHP session. The key is to provide
a lightweight method of ensuring that whichever server processes the
request has access to the session data.
On Fri, Mar 18, 2011 at 11:58 AM, Richard Quadling wrote:
> On 18 March 2011 17:36, Nathan Nobbe wrote:
> > On Fri, Mar 18, 2011 at 11:19 AM, Stuart Dallas wrote:
> >
> >> On Friday, 18 March 2011 at 17:14, Torsten Rosenberger wrote:
> >>
> >> > I'm curious to know what people are storing in the
On Fri, Mar 18, 2011 at 11:56 AM, Stuart Dallas wrote:
> On Friday, 18 March 2011 at 17:36, Nathan Nobbe wrote:
> On Fri, Mar 18, 2011 at 11:19 AM, Stuart Dallas wrote:
> > > On Friday, 18 March 2011 at 17:14, Torsten Rosenberger wrote:
> > > > > I'm curious to know what people are storing in th
On 18 March 2011 17:36, Nathan Nobbe wrote:
> On Fri, Mar 18, 2011 at 11:19 AM, Stuart Dallas wrote:
>
>> On Friday, 18 March 2011 at 17:14, Torsten Rosenberger wrote:
>>
>> > I'm curious to know what people are storing in their sessions. Is there
>> anything larger than a few hundred bytes that
On Friday, 18 March 2011 at 17:36, Nathan Nobbe wrote:
On Fri, Mar 18, 2011 at 11:19 AM, Stuart Dallas wrote:
> > On Friday, 18 March 2011 at 17:14, Torsten Rosenberger wrote:
> > > > I'm curious to know what people are storing in their sessions. Is there
> > > > anything larger than a few hundre
On Fri, Mar 18, 2011 at 11:19 AM, Stuart Dallas wrote:
> On Friday, 18 March 2011 at 17:14, Torsten Rosenberger wrote:
>
> > I'm curious to know what people are storing in their sessions. Is there
> anything larger than a few hundred bytes that is specific and unique to that
> session storage? Wh
On Friday, 18 March 2011 at 17:14, Torsten Rosenberger wrote:
> "Stuart Dallas" schrieb:
>
> > On Friday, 18 March 2011 at 16:19, Torsten Rosenberger wrote:
> > Hello
> > >
> > > First you need to decide which type of cluster you choose. If you use LVS
> > > you can tell the director do bind on
"Stuart Dallas" schrieb:
>On Friday, 18 March 2011 at 16:19, Torsten Rosenberger wrote:
>Hello
>>
>> First you need to decide which type of cluster you choose. If you use LVS
>> you can tell the director do bind one client to one server so you do not
>> need to replicat session.
>
>As I sai
On Friday, 18 March 2011 at 16:19, Torsten Rosenberger wrote:
Hello
>
> First you need to decide which type of cluster you choose. If you use LVS you
> can tell the director do bind one client to one server so you do not need to
> replicat session.
As I said in my response to Tedd, binding clie
Hello
First you need to decide which type of cluster you choose. If you use LVS you
can tell the director do bind one client to one server so you do not need to
replicat session.
If you choose DNS for load balancing you should replicat the session by
database or DRBD or memcache server. Also t
At 3:53 PM + 3/18/11, Stuart Dallas wrote:
Hi Tedd,
Long time no chat, hope you're well.
On Friday, 18 March 2011 at 15:44, tedd wrote:
At 3:18 PM + 3/17/11, Stuart Dallas wrote:
>
> > Pragmatically speaking though, I'd say go for database backed
> sessions until
> > they actually
Hi Tedd,
Long time no chat, hope you're well.
On Friday, 18 March 2011 at 15:44, tedd wrote:
> At 3:18 PM + 3/17/11, Stuart Dallas wrote:
> >
> > > Pragmatically speaking though, I'd say go for database backed
> > sessions until
> > > they actually become a performance bottleneck.
> > -sni
At 3:18 PM + 3/17/11, Stuart Dallas wrote:
> Pragmatically speaking though, I'd say go for database backed
sessions until
> they actually become a performance bottleneck.
-snip-
This may also be of interest:
http://stut.net/2008/07/26/sessionless-sessions-2/
-Stuart
--
Stuart Dall
Stuart, actually I stumbled upon and read your article right after posing
the question to the list, it was definitely a solution I was willing to go
with, I still may do that.
Thank you.
Alessandro
On Thu, Mar 17, 2011 at 11:18 AM, Stuart Dallas wrote:
> On Thursday, 17 March 2011 at 15:15, Nath
On 17 March 2011 16:45, Stuart Dallas wrote:
> On Thursday, 17 March 2011 at 16:16, Richard Quadling wrote:
> On 17 March 2011 16:04, Stuart Dallas wrote:
>> > On Thursday, 17 March 2011 at 16:02, Richard Quadling wrote:
>> > On 17 March 2011 15:30, Stuart Dallas wrote:
>> > > > On Thursday, 17
On Thursday, 17 March 2011 at 16:16, Richard Quadling wrote:
On 17 March 2011 16:04, Stuart Dallas wrote:
> > On Thursday, 17 March 2011 at 16:02, Richard Quadling wrote:
> > On 17 March 2011 15:30, Stuart Dallas wrote:
> > > > On Thursday, 17 March 2011 at 15:29, Stuart Dallas wrote:
> > > > On
On 17 March 2011 16:04, Stuart Dallas wrote:
> On Thursday, 17 March 2011 at 16:02, Richard Quadling wrote:
> On 17 March 2011 15:30, Stuart Dallas wrote:
>> > On Thursday, 17 March 2011 at 15:29, Stuart Dallas wrote:
>> > On Thursday, 17 March 2011 at 15:22, Richard Quadling wrote:
>> > > On 17
On Thu, Mar 17, 2011 at 9:03 AM, Joel wrote:
> Take a look at MCache: http://www.mohawksoft.org/?q=node/8
>
> A drop in distributed replacement for php sessions.
>
One important distinction to draw is that distributed != replicated.
Replication is something extra, as the discussion I linked to
On Thursday, 17 March 2011 at 16:02, Richard Quadling wrote:
On 17 March 2011 15:30, Stuart Dallas wrote:
> > On Thursday, 17 March 2011 at 15:29, Stuart Dallas wrote:
> > On Thursday, 17 March 2011 at 15:22, Richard Quadling wrote:
> > > On 17 March 2011 15:18, Stuart Dallas wrote:
> > > > > On
On 17 March 2011 15:30, Stuart Dallas wrote:
> On Thursday, 17 March 2011 at 15:29, Stuart Dallas wrote:
> On Thursday, 17 March 2011 at 15:22, Richard Quadling wrote:
>> On 17 March 2011 15:18, Stuart Dallas wrote:
>> > > On Thursday, 17 March 2011 at 15:15, Nathan Nobbe wrote:
>> > > On Wed, Ma
On Thursday, 17 March 2011 at 15:29, Stuart Dallas wrote:
On Thursday, 17 March 2011 at 15:22, Richard Quadling wrote:
> On 17 March 2011 15:18, Stuart Dallas wrote:
> > > On Thursday, 17 March 2011 at 15:15, Nathan Nobbe wrote:
> > > On Wed, Mar 16, 2011 at 10:06 PM, Alessandro Ferrucci <
> > > >
Interesting. When I went to it I got no such 404 error. Came right up.
Thought-provoking article, too.
N
On Mar 17, 2011, at 10:22 AM, Richard Quadling wrote:
> On 17 March 2011 15:18, Stuart Dallas wrote:
>> On Thursday, 17 March 2011 at 15:15, Nathan Nobbe wrote:
>> On Wed, Mar 16, 2011 at 1
On 17 March 2011 15:18, Stuart Dallas wrote:
> On Thursday, 17 March 2011 at 15:15, Nathan Nobbe wrote:
> On Wed, Mar 16, 2011 at 10:06 PM, Alessandro Ferrucci <
>> alessandroferru...@gmail.com> wrote:
>>
>> > Hello,
>> > I'm curious, what are the most popular methods to perform session
>> > repli
On Thursday, 17 March 2011 at 15:15, Nathan Nobbe wrote:
On Wed, Mar 16, 2011 at 10:06 PM, Alessandro Ferrucci <
> alessandroferru...@gmail.com> wrote:
>
> > Hello,
> > I'm curious, what are the most popular methods to perform session
> > replication across http servers in PHP?
> > I've read about
Take a look at MCache: http://www.mohawksoft.org/?q=node/8
A drop in distributed replacement for php sessions.
Or you could use memcache to do the same thing.
On Thu, Mar 17, 2011 at 12:06 AM, Alessandro Ferrucci
wrote:
> Hello,
> I'm curious, what are the most popular methods to perform sessi
On Wed, Mar 16, 2011 at 10:06 PM, Alessandro Ferrucci <
alessandroferru...@gmail.com> wrote:
> Hello,
> I'm curious, what are the most popular methods to perform session
> replication across http servers in PHP?
> I've read about repcache(memcached module) and Mysql.
> anything else? is there som
I have successfully and efficiently used MySQL-based database session storage
for years, even on a website with 5,000 (very) active simultaneous users. I
would highly recommend it.
N
On Mar 17, 2011, at 9:44 AM, Dan Joseph wrote:
> On Thu, Mar 17, 2011 at 12:06 AM, Alessandro Ferrucci <
> ales
On Thu, Mar 17, 2011 at 12:06 AM, Alessandro Ferrucci <
alessandroferru...@gmail.com> wrote:
> I'm curious, what are the most popular methods to perform session
> replication across http servers in PHP?
>
I personally just use MySQL and the session_set_save_handler() stuff
attached to a class. M
Hello,
I'm curious, what are the most popular methods to perform session
replication across http servers in PHP?
I've read about repcache(memcached module) and Mysql.
anything else? is there some mod_php_session_replication httpd module?
thanks
--
Signed,
Alessandro Ferrucci
38 matches
Mail list logo
