Lastly, when the chat tab is not visible in TB and there are unread messages polling for anything but mentions and DMs is completely stopped. Keywords could in theory still use a stream as noted, but I don't use keywords myself and it was just more convenient to turn everything into polled resources than to also invest time to support the stream for keywords. The initial state is potentially wrong, but that seems fine to me, it will correct itself as soon as you interact with Thunderbird, most likely. I've added 4 observer notifications for that to keep the provider separated from the frontend. The system tries to stay below the Twitter rate limit and reduces polling when the conversation is not focused or the chat tab is invisible for sure. Similarly, incoming DMs are polled too, so when you send a DM and the other side has sent a DM in the mean time, it will arrive out of order. Mentions, keywords and the normal home timeline are polled independently, so their tweets will be added to the timeline in batches. There will always be out of order tweets and messages, just due to how polling works. The TODOs mainly involve trying to avoid out-of-order tweets and DMs as much as possible. There are still a few TODOs left that I'd want to address before asking for a review. Splinter Review This is a much more recent version incorporating much of what we had discussed since the first iteration.
0 kommentar(er)
