Timeline for Custom Streaming Application - Twitch
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 26, 2013 at 1:18 | vote | accept | Howdy_McGee | ||
| Nov 7, 2012 at 2:57 | comment | added | nickles80 | I was referring to the javascript as I am more familiar with javascript and am not completely familiar with PHP conventions. If you are calling an API once per stream to get the info you are wiring up all the http calls for every stream. As a single call not a big deal but can get heavy with multiple calls. These are just guesses though, which I is why I recommended removing this and trying to load data with the js only. Isolate the parts to determine which is slowing you down. Otherwise you will only be guessing at what to fix. | |
| Nov 7, 2012 at 2:39 | comment | added | user555 | As a general rule you should avoid to use the suppress operator (@) to suppress errors. | |
| Nov 7, 2012 at 2:26 | comment | added | Howdy_McGee | Global Javascript Variables or Global PHP Variables? And good call on the cache - I didn't realize that. I don't really see why that PHP line would cause a major issue since it is just getting the data. Probably lowing the call on the ajax request to 60s would help it out. | |
| Nov 6, 2012 at 19:44 | history | answered | nickles80 | CC BY-SA 3.0 |