zosoled / extralifestreamer Goto Github PK

To simplify the setup process, the URL requires only one parameter of ID. The participant data can then be called which includes the team ID, if any, which can then be subsequently used in team callouts. Participant is asynchronous, so the first team callout fails because participant has not yet returned any data.

Endpoints now serve participant donations and team donations in pages, up to 100 records per page. Total pages are the x-total-records response header.
https://www.extra-life.org/index.cfm?fuseaction=cms.page&id=1353

Refresh rate limit of 60 seconds is intended for an endpoint as a whole, recursively calling an endpoint to get through all data pages can be performed as fast as necessary.
http://community.extra-life.org/forums/topic/7464-donordrive-ama-w-the-extra-life-community/?tab=comments#comment-27629

Hey! I tried messaging you on Discord, but I'm not sure you're on :[

When DataRequester initially populates the data set, team data is being retrieved but nothing is being done with it.

Might I suggest delineating between "team" level functions and "individual" functions (perhaps creating separate entry points via the ExtraLifeStreamer.html launcher?). Is this something you'd like me to take a crack at in a PR?

Changes to how HTTP endpoints are determined and executed broke the connection to team endpoints. Currently it is assumed that a participant ID is sent, but the team callouts need their own team ID.

So far, the simplest way to get the participant ID seems to be a URL parameter. It doesn't require modifying any files manually, it doesn't involve maintaining cookies or storage, and it can be entered directly into the BrowserSource URL options when setting up the source in OBS.