It's internal to the event manager, but an "interest" in a named event
persists until the connection is closed.
In case I wasn't clear, the event notification call is one-shot -- one
registration, at most one notification.
There probably is a cancel event call, but it isn't anything you normally
need to do.
Dimitry is absolutely correct. Like every call in every API in the history
of computing, if you give it bad inputs you can expect bad outputs.
On Wednesday, June 11, 2014, Jiri Cincura <[email protected]> wrote:
> On Wednesday, June 11, 2014, Jim Starkey <[email protected]
> <javascript:_e(%7B%7D,'cvml','[email protected]');>> wrote:
>
>> The event count mechanism makes the system reliable -- if an event is
>> posted between the time notification is delivered and a subsequent
>> registration call, the subsequent call will return immediately with an
>> updated buffer.
>>
>
> Thanks. Do I understand it correctly that aftet the notification is
> delivered the client needs to re-register? Similar stuff is in .NET and
> confuses me a bit. Also looks like the race condition is exactly in this.
>
>
> --
> Jiri {x2} Cincura
> http://blog.cincura.net/ | http://www.ID3renamer.com
>
--
Jim Starkey
------------------------------------------------------------------------------
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing & Easy Data Exploration
http://p.sf.net/sfu/hpccsystems
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
