Missbehaviour of TSimpleIPCServer.GetStringMessage
Original Reporter info from Mantis: Yogi
-
Reporter name: Joachim Paepke
Original Reporter info from Mantis: Yogi
- Reporter name: Joachim Paepke
Description:
In TSimpleIPCServer when You read the property StringMessage and a new incoming string was shorter than any string which came earlier, then the resulting string is not correct.
Example: First received string 'aaa', result will be 'aaa'
Next string 'bbbbbb', result will be 'bbbbbb'; correct
Next string 'ccc', result will be 'cccbbb'; not correct
Next string '1', result will be '1ccbbb'; not correct
Attached patch corrects this, but I am afraid of that anything else would rely on this behaviour? For me it is working good.