fix "Unexpected wire type" error caused when message spans across multiple requests

[eithed]

There's a couple of changes here:

• I don't think do/while loop is necessary as each packet from ES will trigger onNext
• in $dataLength > $messageLength case we've a scenario where one packet contains end of one message and beginning of another - as such currentMessage should become the remainder of $value
• in else case we already have added currentMessage to value - in case where a message spans multiple packets, this will causes following (let's assume our message spans across multiple packets and is ABCD);

1. $value = A at the beginning $this->currentMesage is null at the end $this->currentMessage becomes A
2. $value = B from previous call $this->currentMessage is A at the beginning $value becomes AB at the end $this->currentMessage becomes AAB
3. $value = C from previous call $this->currentMessage is AAB at the beginning $value becomes AABC at the end $this->currentMessage becomes AABAABC

At any point $dataLength > $messageLength condition can be encountered; it fails to decompose the message, because it was incorrectly assembled.

[Th3Mouk]

I'm agree with U, the #18 is IMO more understandable and don't need do/while. I don't get the point, why this do/while has been implemented at the beginning.

[eithed]

@Th3Mouk - would it be worth creating a release?

[Th3Mouk]

@eithed yep absolutely i'm just looking if i can include something else in the release

[Th3Mouk]

just released 3.0.1