Swiftdiff options
| author | Tobias Markmann <tm@ayena.de> | 2017-03-13 09:01:54 (GMT) |
|---|---|---|
| committer | Kevin Smith <kevin.smith@isode.com> | 2017-03-15 11:44:46 (GMT) |
| commit | 87d5f54a90f2759aae587f01650e44aee8f2fe3f (patch) | |
| tree | c84015f0343228aba73642fdd2adc6322631f937 /Swiften/FileTransfer/ByteArrayWriteBytestream.h | |
| parent | 3368a6e5f220f00e03b3ebb41bdd8872ffdf81be (diff) | |
| download | swift-87d5f54a90f2759aae587f01650e44aee8f2fe3f.zip swift-87d5f54a90f2759aae587f01650e44aee8f2fe3f.tar.bz2 | |
Do no emit onXMPPDataRead when the session is terminated
On a bosh error BOSHSessionStream, posts an event to the event
loop that closes the XMPP stream. If onXMPPDataRead is
emitted, that data is handled before the close of the stream
though, which can cause another BOSH request to be sent.
Test-Information:
Added a unit test verifying the behaviour.
Wrote a custom python script replicating the original error
and verified that Swift does not stay connected on a BOSH
error with additional text data.
Tested on macOS 10.12.3 with recent clang trunk.
Change-Id: Ie90099afa0934707a6758b00706a65227ceb48b8
Diffstat (limited to 'Swiften/FileTransfer/ByteArrayWriteBytestream.h')
0 files changed, 0 insertions, 0 deletions