The opera_auth module contains the code for doing authentication with Link and Unite.
API documentation generated by Doxygen contains all necessary information for the external APIs.
API documentation generated by Doxygen contains information about the internal organization of the module.
The module is rather small. It can be enabled and disabled using the FEATURE_OPERA_AUTH feature.
All the functions handle OOM by returning a status to the caller.
There is no particular OOM handling. A failure code is returned to the caller, which is expected to exit with a failure code of its own.
An authentication request uses the g_transferManager to initiate a HTTPS request. On completion of the request, the result is analyzed and a listener callback is called.
No sizeable heap memory used.
No sizeable stack memory used.
No sizeable static memory used.
No caching used.
Memory is freed on exit.
No temp buffers used.
Nothing to tune.
None.
A successful authentication would exercise a lot of code. However, it is not feasible to put this in a selftest
Due to usage in desktop, the old OperaAuthentication interface remains in a backwards compatible form. However, as this API has some limitations it has been replaced by the CoreOperaAccountManager API which is a back-end for the DOM_OperaAccountManager interface. This new API completely hides the old implementation.
At present, no improvments are planned.