Writing your own JSON code to pull your participant data or your team's data out for use on your stream or other places? Share your code with the rest of the community! Looking for a code snippet to do something specific? Ask for it here.
Extra Life United is a gaming event like no other. Participants compete in a gaming tournament on behalf of their local Children’s Miracle Network Hospital, meet the children they support by being a part of Extra Life and connect with other Extra Lifers from across the globe. The tournament features popular tabletop and video games that everyone enjoys!
Ask your question and have it answered by other Extra Lifers. You can vote on which answer is best so other members can see your question and the best answer. This area functions much like a live FAQ that is constantly updated by the Extra life Community.
You *shouldn't* be, but I can't rule it out. If you'd like to DM me with some network info, I can take a look. You can find me over on the #donordrive-support Discord channel.
As far as polling strategy, let me walk you through what we do internally. We leverage the `etag` + `if-none-match headers` to determine the need to poll "subordinate" endpoints. Using the participant + participant donors model above, you can poll the /participants/XXX endpoint on your 30 second intervals furnishing the `if-none-match` header. If you get a 200, then that means something changed (you'll get a 304 if nothing has changed), you can subsequently compare `participant.sumDonations` with your previous iterations `participant.sumDonations`. If the values aren't equal, you know there are new donations to fetch, otherwise, you dont even need to bother polling /donations.
The ancillary benefit of this route, is that you don't have to assume a refresh (and subsequently the parsing/rendering overhead) of your assets on every polling interval.
Hope this helps,
Different issue I'm noticing. Maybe I'm hitting the API too much post DDOS? But I amd getting connection timeout errors. If you could take a quick peek and let me know what you think -
I haven't changed anything in extralifedonations.py since before the DDOS. Lines 172-203 govern the loop. I have it sleeping 30 seconds between each iteration. However, within that 30 seconds I hit at least 4 times - participant, donors, team, team donors. Is that too much now? Is there a more efficient way that's more compliant in the post-DDOS world?