Hi Mike,
Do you have a sample of this sort of scenario? I'd like to try it out and then see if we can maybe log feature to allow the InfoMessageHandler release received results as they arrive.
Also, with discussion internally, we do handle certain sev 10 as errors (off-hand I don't know which ones) and investigating if this condition, since ASE sends abort mesg and does abort the command, should be handles in AseException. However, there is risk we might affect other applications developed that do handle with infomessage handler.
If you folks here want to consider such an enhancement (and for a more responsive handling of results when under the auspices of InfoMessageHandler, please log incident at SAP under BC-SYB-SDK and we can log them.
Cheers,
-Paul