MAXSTEELTURBOGO / facebook-actionscript-api

Automatically exported from code.google.com/p/facebook-actionscript-api
0 stars 0 forks source link

FacebookXMLParserUtils > "toDate" function returns different time/date #49

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. fbook.post(new GetEvents(fbook.uid,null,yesterday));
2. for loop through.. "responseData.eventCollection.getItemAt
(i).start_time"
3.compare specific event's start time (on facebook) with the GetEvents 
data start_time

What is the expected output? What do you see instead?
time/date as listed on actual event listing. 3 hours ahead.

What version of the product are you using? On what operating system?
3.1 / Vista

Please provide any additional information below.
My computer's clock reads E.S.T. (GMT - 4:00). 
Facebook seems to list their User's timezone as GMT -"The time offset 
relative to GMT (e.g., California is -8)." : 
http://wiki.developers.facebook.com/index.php/Users.getStandardInfo
while their event times are listed as UTC "An integer representing the 
number of seconds since January 1, 1970 (UTC). Commonly known as "unix 
time." : http://wiki.developers.facebook.com/index.php/Time#time
While confusing, This would make sense to me if the returned start_time 
were -4 rather than -3. 
As well, I am leaving "end_time" out of the GetEvents function call 
because it returns wildly varying results.

I am guessing the string you are converting in the toDate function is 
already relative to the event's locale since it is not already a date or 
number.

Your response/help would be greatly appreciated, as is your work.

Keylo.

Original issue reported on code.google.com by wholenew...@gmail.com on 22 May 2009 at 7:42

GoogleCodeExporter commented 9 years ago
about the start_time,end_time problem:

part of problem with supplying start_time,end_time params to GetEvents call is 
that 
facebook API does not list an "ongoing" query for events. 

Ex:
Event creators opts for repeating weekly events, lets say every Wednesday from 
April 
through June, this being May. 
Unless the getEvents call is open to sifting over start times of a month ago 
and 
leaving end times open, we will not get the event.
This slows things to a crawl when each eid needs to be called upon for its 
data, and 
in my case, each uid's events extracted from between longer periods of time.

Is there an "ongoing event" tag floating around that can easily be queried?
It would be useful if there could be a Boolean value added to the call for such 
a 
thing so that we could narrow the getEvents parameters down to a minimum, but 
would 
recognize ongoing events that start and end outside of the parameters. 

Original comment by wholenew...@gmail.com on 27 May 2009 at 4:05

GoogleCodeExporter commented 9 years ago
New release based of Facebook's Graph API is coming soon.  SDK which this issue 
depends on is no longer supported by Facebook.

Original comment by alan...@gmail.com on 29 Sep 2010 at 7:49