Vasily Khoruzhick wrote: > Hi, Daniel > > I have two questions: > > 1. Maybe it will be better if libfprint will support different storages > directly? Is there any special reason to move this functionality to the > fprintd?
I'd like to keep libfprint simple and focused purely on fingerprint scanning. Storage adds a lot of complications. LDAP, MySQL, encryption, DAV, etc. > 2. Is there any docs for async API? If I understand correctly, user of async > API should use following scheme, am I right? There is no documentation yet. fprint_demo and fprintd are 2 examples you can look at though. Your usage of the async API depends on the application. If you need to mix with other event sources then you need to get the file descriptors and add them to your main loop, and consider libfprint's next timeout. But if fprint is your only event source then you can just call fp_handle_events() in a simple loop - no need to call poll() or select(). If you call poll() or select() and determine activity on fprint event sources then you should call fprint_handle_events_timeout with a zero timeout. Same applies if you determine that fprint's next timeout has expired. Daniel _______________________________________________ fprint mailing list [email protected] http://lists.reactivated.net/mailman/listinfo/fprint
