Thread support statement

BlackBerry Dynamics applications can make use of the concurrent execution features provided by the operating system. However, there are certain BlackBerry Dynamics activities that all must take place in the same thread. These are listed below. The thread is referred to as the BlackBerry Dynamics thread. It will be the application main thread.

End-User Authorization

The authorize (GDiOS) functions must be called in the BlackBerry Dynamics thread. The authorize (GDiOS) event-handling delegate callbacks will be executed in the BlackBerry Dynamics thread.

Push Notification

All GDPushChannel objects must be initialized in the BlackBerry Dynamics thread, and only have their methods called in that thread. Their event-handling delegate callbacks will be executed in the BlackBerry Dynamics thread.

Secure socket communication

GDSocket objects may be initialized in any thread, and have their methods called in any thread. Their event-handling delegate callbacks will be executed in the BlackBerry Dynamics thread.

Secure HTTP communication

GDHttpRequest (deprecated) objects may be initialized in any thread, and have their methods called in any thread. Their event-handling delegate callbacks will be executed in the BlackBerry Dynamics thread. Note that synchronous requests should not be made from the application main thread.

The following BlackBerry Dynamics activities may take place in any thread: Secure SQL Database access, Secure File System access.

See also

Concurrency Programming Guide on the apple.com developer website.