Ok, so I've been brewing on this for awhile. Recently, Yahoo laid off many people from its various services, including Upcoming. As it stands, it looks like the better approach is to use the YQL API instead of querying upcoming directly.

Why is this better? Don't need an API key, the tables are public. Much less complicated to get out events.

Drawbacks? Limited to < 5k queries/day or some such number. Could fall back to developer api key or something at that point.

So, my position here is I am going to change the 6.x. release to use my recently released YQL API module. Read up at http://drupal.org/project/yql

Comments

coderintherye’s picture

coderintherye commented

Forgot to add this would be only for pulling events. For pushing/adding events into Upcoming the approach would still be to use the API. But now that I think about it, that seems to be the original intent of this module anyways, to be a push module. So it may fit better to have a pull module as a separate plugin to the YQL API. I'm open to either option.

ipwa’s picture

ipwa commented

Hey, sorry for taking long to answer. Let's just do it all in here as a wrapper, we can have a sub module called upcoming_event_post or something and have that depend on yql so people can still continue to use this module as it is.... Hmmm actually now that I'm writing this down let's make both have the dependency and forget about the key, it will be helpful to more people if they could just install it and have everything straight up without registering to anything. Thanks this is good stuff. :)

ipwa’s picture

ipwa commented

Fall back on developer key sounds cool.

coderintherye’s picture

coderintherye commented

Coolness, yeah I like falling back on the developer key. Yeah, basically the problem I see with upcoming_event as it is currently is it is hard to get going right away cause there is a lot of setup, and so this will help people get going to pull down events, and then they'll say, oh and now I want to add events, so let's go get an API key and get that setup.

Admittedly, my plate is full this week due to having been at Drupalcon, so probably won't get to this until next week.