On 26/02/2015 11:11, Dmitry Yemanov wrote: > 26.02.2015 16:55, Adriano dos Santos Fernandes wrote: > >> For example, there is example UDR who waits for an event, blocking the >> calling. > I don't think Carlos wants to block the caller.
That is just the example currently done. It should be adapted. > Also, if the caller > dies, notifications will be lost until someone notices that and > reconnects and restarts the UDR. The UDR can be called in ON CONNECT. > Special attention is also needed to > avoid multiple callers/UDRs acting as subscribers simultaneously. > > It seems you talk about different feature than he, i.e., a single registration who is going to process events in the server? As he explained now, he just wants to cache values in variables, so I think an ON CONNECT + UDR + events + SP is going to work well. Adriano ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
