make transport configurable for streaming api #2224
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@zregvart can you give a look? |
|
Can you raise a Jira to trace the problem @sebbeaume ? |
|
@zregvart this looks good to me. I'll wait for your feedback. |
|
I've polished this a bit and committed it to in 4eb0a75 to |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The goal of this PR is to make the LongPollingTransport configurable through the SalesforceComponent.
The need encoutered is :
While using the streaming api (PushTopic), we sometimes receive a message of a size exceeding the BufferingResponseListener maxLength property.
Enabling configurating the LongPollingTransport will give the possibility to control the authorized maxLength.