Issue a read, but dont consume all of the events. e.g. call FirstOrDefaultAsync or otherwise only enumerate some of the events before returning/throwing out of the foreach. The call remains open indefinitely. If the server is waiting to send more events to the client then the call will count towards the relatively low concurrent call limits, otherwise it will only remain open on the client, occupying some memor.
Issue a read, but dont consume all of the events. e.g. call FirstOrDefaultAsync or otherwise only enumerate some of the events before returning/throwing out of the foreach. The call remains open indefinitely. If the server is waiting to send more events to the client then the call will count towards the relatively low concurrent call limits, otherwise it will only remain open on the client, occupying some memor.
Cancelling does cause the call to end