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.

Sign up for GitHub

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

Jump to bottom

Use persistent senders by default #141

Closed
felix-hilden opened this issue Feb 2, 2020 · 0 comments
Closed

Use persistent senders by default #141

felix-hilden opened this issue Feb 2, 2020 · 0 comments
Assignees
@felix-hilden
Labels
change Change behaviour of an existing component
Milestone
v2.0.0

Comments

@felix-hilden
Copy link
Owner

Currently, transient senders provide the most vanilla sending. Persistent senders are quite similar out of the box, but share connections. This improves performance quite a bit and should be the default. We shouldn't remove transient senders, but I guess they'll simply be the suboptimal solution from that point on.
@felix-hilden felix-hilden added the change Change behaviour of an existing component label Feb 2, 2020
@felix-hilden felix-hilden added this to the v2.0.0 milestone Feb 2, 2020
@felix-hilden felix-hilden self-assigned this Feb 2, 2020
@felix-hilden felix-hilden mentioned this issue May 7, 2020
Merged
11 tasks
felix-hilden added a commit that referenced this issue May 7, 2020
@felix-hilden
Default to PersistentSender, fixes #141
e694b4a
felix-hilden added a commit that referenced this issue May 17, 2020
@felix-hilden
Default to PersistentSender, fixes #141
7c5bf3a
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@felix-hilden felix-hilden

Labels
change Change behaviour of an existing component
Projects
None yet
Milestone
v2.0.0
Development

No branches or pull requests
1 participant
@felix-hilden