Re: [nyphp-talk] Backups of session files

2011-10-04 Thread Greg Rundlett (freephile)
On Tue, Oct 4, 2011 at 4:56 PM, Hans Zaunere wrote: > > I'm curious whether it's worthwhile to backup PHP session stores. > > I would say no... the nimble session and lethargic backup/restore models > just don't fit in my opinion. > > > At first I thought, why do that? But then I figured that if

Re: [nyphp-talk] Backups of session files

2011-10-04 Thread Hans Zaunere
> I'm curious whether it's worthwhile to backup PHP session stores. I would say no... the nimble session and lethargic backup/restore models just don't fit in my opinion. > At first I thought, why do that? But then I figured that if the session > can last a long time (e.g. 60 minutes) AND if a r

[nyphp-talk] Backups of session files

2011-10-04 Thread Greg Rundlett (freephile)
I'm curious whether it's worthwhile to backup PHP session stores. At first I thought, why do that? But then I figured that if the session can last a long time (e.g. 60 minutes) AND if a restore from some service failure was done quickly, then it MIGHT be worthwhile to include your session directo

Re: [nyphp-talk] somewhat OT Re: validating proper name capitalization

2011-10-04 Thread Tedd Sperling
On Oct 4, 2011, at 1:13 PM, John Campbell wrote: >> I understand that, but I'm asking something like: if you type in •.com into >> your browser, what's getting passed to the server behind the scenes? > > The non encoded string (xn--...). It must be this way because the > HTTP protocol requires t

Re: [nyphp-talk] somewhat OT Re: validating proper name capitalization

2011-10-04 Thread Jerry B. Altzman
on 10/4/2011 1:13 PM John Campbell said the following: I understand that, but I'm asking something like: if you type in •.com into your browser, what's getting passed to the server behind the scenes? The non encoded string (xn--...). It must be this way because the HTTP protocol requires the he

Re: [nyphp-talk] somewhat OT Re: validating proper name capitalization

2011-10-04 Thread John Campbell
> I understand that, but I'm asking something like: if you type in •.com into > your browser, what's getting passed to the server behind the scenes? The non encoded string (xn--...). It must be this way because the HTTP protocol requires the header to be completely US-ASCII. It is best to think

Re: [nyphp-talk] somewhat OT Re: validating proper name capitalization

2011-10-04 Thread Jerry B. Altzman
on 10/3/2011 5:17 PM Tedd Sperling said the following: PUNYCODE is the ULR for IDN (Internationalized Domain Names). PHP doesn't have to deal with it any more/less than any other URL. I understand that, but I'm asking something like: if you type in •.com into your browser, what's getting pass