[SSSD] ELAPI fundamental architectural issue

Stephen Gallagher sgallagh at redhat.com
Fri Nov 20 20:11:16 UTC 2009


-----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 right
> away using the dispatcher's internal loop. I think we should not do
> anything for this use case and if the app wants to do something like
> this the app developer needs to use two dispatchers. 
> 
> Steve do you agree?
> 

Yes, I was talking about the hypothetical case where everything has
gotten shot straight to hell and the application wants to fire a log
right *bleep*ing now before getting back into the mainloop and dying
completely.

But for this (admittedly extreme) case, I think a separate dispatcher is
an acceptable solution.

- -- 
Stephen Gallagher
RHCE 804006346421761

Delivering value year after year.
Red Hat ranks #1 in value among software vendors.
http://www.redhat.com/promo/vendor/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iEYEARECAAYFAksG998ACgkQeiVVYja6o6O/swCfZtgKkijVYFNT/OXTp+E2nnJb
sB0AmwYXTMQRXaKyKRvfqPlljQgCvG2N
=pRtg
-----END PGP SIGNATURE-----



More information about the sssd-devel mailing list