[fprint] why enum fp_finger?
Joshua N Pritikin
jpritikin at pobox.com
Fri Sep 25 02:16:42 BST 2009
On Thu, Sep 24, 2009 at 08:52:26PM +0300, Artem Egorkine wrote:
> On Thu, Sep 24, 2009 at 6:21 PM, Joshua N Pritikin <jpritikin at pobox.com>wrote:
> > Regardless of FAR rates, I am skeptical that enum fp_finger belongs in
> > the API. The header might include enum fp_finger, but why should any
> > functions use it?
>
> I agree with you, but libfprint tries to be a bit more than a library
> providing access to the finger print scanner. If you look closely, it also
> handles storage (saving and loading) of fingerprint data for any given user
> in their home directory. And this functionality allows the application to
> store a fingerprint binding it to whichever finger it belongs to, so that
> the verification process can return this "id".
Yah, this part of the library seems like it ought to be split off into a
separate libfprint-storage library or something. It's really not central
to what libfprint is designed to do.
More information about the fprint
mailing list