× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Lol, restart your NEPS!

-Eric DeLong

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Gary Thompson
Sent: Monday, March 12, 2012 1:23 PM
To: Midrange Systems Technical Discussion
Subject: RE: How can a program find out whether a system is on Daylight Saving Time?

So, >maybe< your server is daylight saving time and,
the web service is not dst?
Or, >maybe< your web service interface does not correctly
identify your time zone?

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of James Lampert
Sent: Monday, March 12, 2012 12:14 PM
To: Midrange Systems Technical Discussion
Subject: How can a program find out whether a system is on Daylight Saving Time?

The subject line says it all. My Google Calendar Interface has started blowing up, and I've determined that it's happening because the C time() function (which is used in generation of the digital signature for the web service request) is now returning a time number that is one hour in the future. And the Google Calendar web services are rejecting it.

If I run the request out of OAuth Playground, the time number is 3600 seconds earlier than what I get on the 400, and if, in the debugger, I manually subtract 3600 seconds from the time number, it works just fine, which makes the above diagnosis look pretty conclusive.

--
JHHL

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.