Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: Preparing for 3.3.0 release #215

Merged
merged 1 commit into from
Oct 22, 2019
Merged

Conversation

aliabbasrizvi
Copy link
Contributor

No description provided.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 97.694% when pulling a6accdf on ali/prep_for_3_release into aa2eca3 on master.

2 similar comments
@coveralls
Copy link

Coverage Status

Coverage remained the same at 97.694% when pulling a6accdf on ali/prep_for_3_release into aa2eca3 on master.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 97.694% when pulling a6accdf on ali/prep_for_3_release into aa2eca3 on master.

Copy link
Contributor

@mikeproeng37 mikeproeng37 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

* Events generated by methods like `activate`, `track`, and `is_feature_enabled` will be held in a queue until the configured batch size is reached, or the configured flush interval has elapsed. Then, they will be batched into a single payload and sent to the event dispatcher.
* To configure event batching, set the `batch_size` and `flush_interval` properties when initializing instance of [BatchEventProcessor](https://github.com/optimizely/python-sdk/blob/3.3.x/optimizely/event/event_processor.py#L45).
* Event batching is disabled by default. You can pass in instance of `BatchEventProcessor` when creating `Optimizely` instance to enable event batching.
* Users can subscribe to `LogEvent` notification to be notified of whenever a payload consisting of a batch of user events is handed off to the event dispatcher to send to Optimizely's backend.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are there dev docs we can link to here?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

They are in staging. May be useful to reference them in README later on.

@aliabbasrizvi aliabbasrizvi merged commit 77ec185 into master Oct 22, 2019
@aliabbasrizvi aliabbasrizvi deleted the ali/prep_for_3_release branch October 22, 2019 20:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants