Re: [Firebird-net-provider] Firing event when event count is 0

If the event you mentioned means, "nothing happens, I'm just alive and send you this", then you should only fire some event that means server alive, nothing else. No one cares that event occurs just because server sent something. On 17 December 2016 at 00:22, Si Carter wrote:

Re: [Firebird-net-provider] Firing event when event count is 0

No it doesn't make sense, a bit like saying "look, nothing happened" but here you go anyways... On 16 Dec 2016 15:15, "Jiří Činčura" wrote: > Hi *, > > As I'm now reworking some pieces in events (together with finalizers), > I'm wondering whether it make sense to fire the

Re: [Firebird-net-provider] Firing event when event count is 0

Server sends whole buffer with all registered events. Some are sometimes obviously 0 (or actually last count, because in server it's incremental), if not fired, but still in buffer. -- Mgr. Jiří Činčura Independent IT Specialist On Fri, Dec 16, 2016, at 15:48, Ivan Arabadzhiev wrote: >

Re: [Firebird-net-provider] Firing event when event count is 0

Why would the engine throw such an event in the first place? Does it have an actual reason or is it a bug to be fixed? I don't think the provider should just ignore server messages sent on purpose, but there might be an actual option on whether the current user actually needs them or not.

Re: [Firebird-net-provider] Firing event when event count is 0

I say ney. It doesn’t make sense to raise unraised events. Sent from Mail for Windows 10 From: Jiří Činčura Sent: vrijdag 16 december 2016 17:15 To: For users & developers of the Firebird .NET

[Firebird-net-provider] Firing event when event count is 0

Hi *, As I'm now reworking some pieces in events (together with finalizers), I'm wondering whether it make sense to fire the event for events when the event count was 0. From outside POV it doesn't make much sense. What do you think? -- Mgr. Jiří Činčura Independent IT Specialist