This is a discussion on Re: does ASN1_UTCTIME_get() changes by local time zone settings - Openssl ; That is right but what I thought was that if I can get the time_t then it will be even better for performance to just check it every time, because if for example I want to check if one hour ...
That is right but what I thought was that if I can get the time_t then
it will be even better for performance to just check it every time,
because if for example I want to check if one hour past I will need to
get the time, and then to calculate it against the last time and then
compare it to a number that represent 1 hour, I thought instead I can
get the time and compare it to the time_t of the expiration that I
already saved (may be a year a ago in the cache).
On 1/29/06, Dr. Stephen Henson
> On Sat, Jan 28, 2006, Joe Gluck wrote:
> > Any ideas, the ASN1_cmp_time does much more than what I need, because
> > I will be comparing at least once a second (If I check the last time
> > to be at least one second earlier.) And because they are all in my
> > cache for hopefully lets say a year, why not convert it to time_t and
> > just check it with > current_gmt_time ?
> BTW you don't have to call that function once a second. You can pass any =
> to ASN1_cmp_time(). You could for example pass a time an hour in the futu=
> if it indicated the time wasn't exceeded there would be no point checking=
> for a further hour.
> Dr Stephen N. Henson. Email, S/MIME and PGP keys: see homepage
> OpenSSL project core developer and freelance consultant.
> Funding needed! Details on homepage.
> Homepage: http://www.drh-consultancy.demon.co.uk
> __________________________________________________ ____________________
> OpenSSL Project http://www.openssl.org
> Development Mailing List email@example.com
> Automated List Manager firstname.lastname@example.org
OpenSSL Project http://www.openssl.org
Development Mailing List email@example.com
Automated List Manager firstname.lastname@example.org