Remember that your OddsFeedListener call-backs are handled by a single thread; if you do too much processing within your call-back, subsequent odds messages are delayed as they will not be processed until you finish the call-back processing. The recommended way to handle longer processing times is to put the received messages on a queue, and let them be processed by a different thread. The first time you try to access information about a sport event, the SDK looks up its details using an API-call. This information is cached for subsequent calls. For that reason, the first call for a new sport event may take a bit longer. It is also during this first time call that the various languages you have requested are looked up for the event – so if you have specified multiple languages the first call may take even longer. If you can avoid accessing any non-basic properties, you can avoid longer delays most of the time, as the basic information is normally cached for almost all messages by the SDK. (Basic information is sport, category, tournament, match competitors, scheduled start time). |