So will the world come to an end or will it just weed out the big boys from the
little boys?
Now, I know I’m in trouble. I finally saw Hans message.
From: John Campbell
Sent: Sunday, July 10, 2011 10:57 PM
To: NYPHP Talk
Subject: Re: [nyphp-talk] cookies and experiation
The reason you cannot
I guess I reinvented the wheel.
Hey, John.
From: John Campbell
Sent: Sunday, July 10, 2011 10:57 PM
To: NYPHP Talk
Subject: Re: [nyphp-talk] cookies and experiation
The reason you cannot add 125 years is the 2038 problem. A simple solution is
to set the expiration date to Jan 1, 2038.
ht
Party at my house. I finished my project after working all weekend. No. I’m
not drinking.
Woohoo! Thanks to all those who help especially Jim for saved me for having a
hard-coded value in my code.
Margaret Michele Waldman___
New York PHP Users Gro
Your "solution" will make things worse with google. There is no "duplicate"
content pentalty, but there is a "scraper" penalty, and I doubt that is
being applied in your case. "noindex" tells google that you have a page
that customers can and should see, but the googlebot specifically doesn't
hav
The reason you cannot add 125 years is the 2038 problem. A simple solution
is to set the expiration date to Jan 1, 2038.
http://en.wikipedia.org/wiki/Year_2038_problem
-jc
On Sun, Jul 10, 2011 at 12:13 PM, Margaret Waldman wrote:
> Jim, I used the at 386 from ‘90-‘04. I even put Windows ‘9
On Jul 10, 2011, at 9:14 PM, Michael B Allen wrote:
> Meaning Google was indexing the same exact page
> through two slightly different URLs.
>
> I now generate the pages separately with one containing name="robots" content="noindex"/> (which unfortunately has to be
> index.html because the other
I just found a major mistake in one of my websites. The Google rank
for the primary page has always been inexplicably horrible. Then I
found out that Google decreases the ranking of a page if it contains
content that is largely duplicated elsewhere such as on an adjacent
page. Turns out that index.
Jim, I used the at 386 from ‘90-‘04. I even put Windows ‘95 on it and surfed
the web. Granted it was slowed than you can imagine ...
From: Jim Yi
Sent: Sunday, July 10, 2011 10:44 AM
To: NYPHP Talk
Subject: Re: [nyphp-talk] cookies and experiation
PHP has some useful predefined constants, p
well not of brower specific, but I’ve had several computers crash so I’m fully
aware that most no one will be using that cookie in 68 years.lol
From: Jim Yi
Sent: Sunday, July 10, 2011 10:44 AM
To: NYPHP Talk
Subject: Re: [nyphp-talk] cookies and experiation
PHP has some useful predefined
I’ve thought of all of this ...
- is using the same computer for five years
- has never reformatted the hard drive or re-installed a fresh OS
- has never switched browsers
- has never cleared their cookies
Thanks for PHP_INT_MAX.
From: Jim Yi
Sent: Sunday, July 10, 2011 10:44 AM
To: NYPHP Tal
Hi:
> I found 2147483647 in the documentation, but I saw larger numbers
> working. Hum.
It's platform/operating system dependent. Things tend to get hairy over
2^53. There's bcmath if you need big numbers or significant precision.
--Dan
--
T H E A N A L Y S I S A N D S O L U T I O N
PHP has some useful predefined constants, particularly PHP_INT_MAX in this
case (http://php.net/manual/en/reserved.constants.php). What you should
really be doing while setting the cookie is ignoring time() completely, and
just set the expiration time to the maximum size of an integer.
setcooki
My calcs/prog show
2147483647 really is the biggest int
From: Margaret Waldman
Sent: Sunday, July 10, 2011 9:56 AM
To: NYPHP Talk
Subject: [nyphp-talk] cookies and experiation
I wanted to create a cookie that basically never expires.
time() + x
We can live to say 100 or so, so say 125 years
The NYPHP frontend covers the JavaScript topics.
Hans Kaspersetz
Cyber X Designs
h...@cyberxdesigns.com
http://cyberxdesigns.com
Sent from my iPhone
On Jul 10, 2011, at 9:26 AM, "Margaret Waldman" wrote:
> Well how about a nyphp-talk(javascript) list for php programmers who develop
> in java
I wanted to create a cookie that basically never expires.
time() + x
We can live to say 100 or so, so say 125 years expiration would be good.
time() + 394470
But that number is too big.
Intval says on a 32 bit machine max is 2147483647.
So 2147483647 – time() = 4294967294, which is bigger
Why?
There is already a mailing list - NYPHP SIG: Front End that covers
JavaScript / jQuery /JSON. You can join at nyphp.org
On Sun, Jul 10, 2011 at 9:26 AM, Margaret Waldman wrote:
> Well how about a nyphp-talk(javascript) list for php programmers who
> develop in javascript, too?
>
>
> -Or
Well how about a nyphp-talk(javascript) list for php programmers who develop
in javascript, too?
-Original Message-
From: Kristina Anderson
Sent: Saturday, July 09, 2011 10:04 AM
To: talk@lists.nyphp.org
Subject: Re: [nyphp-talk] Wordpress & Ajax
Let's face it, there is NO other list
I found 2147483647 in the documentation, but I saw larger numbers working. Hum.
From: Margaret Waldman
Sent: Sunday, July 10, 2011 5:09 AM
To: NYPHP Talk
Subject: [nyphp-talk] largest interger
Does anyone know the largest integer in php?
Margaret Michele Waldman
Does anyone know the largest integer in php?
Margaret Michele Waldman___
New York PHP Users Group Community Talk Mailing List
http://lists.nyphp.org/mailman/listinfo/talk
http://www.nyphp.org/Show-Participation
19 matches
Mail list logo
