You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You can initialize the Optimizely instance in three ways: with a datafile, by providing an `sdk_key`, or by providing an implementation of `config_manager.BaseConfigManager`_. Each method is described below.
34
+
You can initialize the Optimizely instance in three ways: with a datafile, by providing an `sdk_key`, or by providing an implementation of `BaseConfigManager`_. Each method is described below.
34
35
35
36
1. Initialize Optimizely with a datafile. This datafile will be used as
36
37
ProjectConfig throughout the life of Optimizely instance.
@@ -41,9 +42,9 @@ You can initialize the Optimizely instance in three ways: with a datafile, by pr
41
42
)
42
43
43
44
2. Initialize Optimizely by providing an 'sdk_key'. This will initialize
44
-
a PollingConfigManager that makes an HTTP GET request to the URL (formed
45
-
using your provided `sdk key` and the default datafile CDN URL
46
-
template) to asynchronously download the project datafile at regular
45
+
a PollingConfigManager that makes an HTTP GET request to the URL
46
+
(formed using your provided `sdk key` and the default datafile CDN URL template)
47
+
to asynchronously download the project datafile at regular
47
48
intervals and update ProjectConfig when a new datafile is received. A
48
49
hard-coded datafile can also be provided along with the `sdk_key` that
49
50
will be used initially before any update.
@@ -101,7 +102,7 @@ You may also provide your own logger, error_handler, or
101
102
notification_center.
102
103
103
104
Advanced configuration
104
-
''''''''''''''''''''''
105
+
''''''''''''''''''''''
105
106
106
107
The following properties can be set to override the default
0 commit comments