[fprint] why enum fp_finger? [RESEND]

[Joshua N Pritikin]

I must be missing something really basic. Why is enum fp_finger part of 
the API? Do people actually enroll all their fingers? If they do, why? 

It seems to me that I want to be identified by a single finger for most 
applications. Perhaps for high security, it would be worth testing more 
than one finger?

If identification frequently has false negatives then it seems like I 
would want multiple versions of a single finger. Why does the API 
directly support multiple fingers but offers no specific support for 
multiple versions of the same finger? Or am I missing something?

Wouldn't it make more sense to remove enum fp_finger and move it to the 
application side (if needed)?

-- 
American? Vote on the National Initiative for Democracy, http://votep2.us