-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/20/2009 03:07 PM, Dmitri Pal wrote:
>
> I was thinking this way too but Steve brought a point that the
> application might want to use the sync interface in this case exactly
> for the reason of bypassing its main loop and sending the event righ
> No I think that apps that use mixed async and sycn logging do so only
> when sending a sync log requires it to know the operation went through.
>
Ok so I will add a queue at the beginning... Ohh. More complexity and
more work...
> In that case the application is prepared to wait the time it
On Fri, 2009-11-20 at 14:27 -0500, Dmitri Pal wrote:
> If I understand you correctly you agree that having an internal queue
> is
> the right approach.
>
> Do you agree with the recommendation to use different dispatchers if
> application wants to log sync and async events at the same time?
No. I
Simo Sorce wrote:
> On Fri, 2009-11-20 at 12:50 -0500, Dmitri Pal wrote:
>
>> b) Hold the events in queue inside ELAPI dispatcher and let them go
>> through the whole sink chain only one at a time. In this case there
>> will
>> be only one event traveling the callbacks at a time. This approach
>
On Fri, 2009-11-20 at 12:50 -0500, Dmitri Pal wrote:
> b) Hold the events in queue inside ELAPI dispatcher and let them go
> through the whole sink chain only one at a time. In this case there
> will
> be only one event traveling the callbacks at a time. This approach
> though avoids the blocking o
Hi,
I am pretty close to having ELAPI based on the async processing to at
least building.
This means that I finally embraced the logic or async programming and
managed to understand what should be done where and how.
Big progress I should say. So...
The events now can be created and logged asynchr
