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:
> No it doesn't make
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 event for events when
>
oft.com/fwlink/?LinkId=550986> for
> > Windows 10
> >
> >
> >
> > *From: *Jiří Činčura
> > *Sent: *vrijdag 16 december 2016 17:15
> > *To: *For users & developers of the Firebird .NET providers
> >
> > *Subject: *[Firebi
Činčura
> *Sent: *vrijdag 16 december 2016 17:15
> *To: *For users & developers of the Firebird .NET providers
>
> *Subject: *[Firebird-net-provider] Firing event when event count is 0
>
>
> Hi *,
>
> As I'm now reworking some pieces in events (together with f
.NET
providers<mailto:firebird-net-provider@lists.sourceforge.net>
Subject: [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
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
-
