I think I know the answer now ( after our somewhat prolong discussion about merits of fpusb ), but I want to ask the question anyhow. Do you not consider relines to glib ( and imageMagik to some degree ) to be bad thing? I guess if your development efforts are solidly centered on Linux, it is not such a big deal to you. Still, considering the fact that very small number of functions from glib actually used by fprint ( 26 ) and that only memory allocation/linked list management functions used for "core" operations in libfprint and considering that rest of functions are mostly concern file/directory manipulations and have equivalents available among standard C functions and especially considering the fact that as I have noticed, you decide NOT to use glib for list management in fpusp - is there any chance that this dependency (on glib) will go away in the future?
Sort of along the same lines ... should fprint really use NIST code in such a "intimate" way? NIST is free/open source/good, but it is not the only recognition package. What if someone will want to use some other package? What if some one will not want to use ANY recognition package at "scanner side" of authentication chain? Will it be nice to have ability to swap minutia extraction/matching algorithms easily? Something similar to the way different drivers get "registered" (I do realize that most often only one finger recognition set of algorithms will be needed, so it just a question of switching from one to another). It is even more awkward, considering the fact that many fingerprint scanners luck imaging ability altogether, so NIST (or any other recognition software) is rather useless when coupled with such scanner. Andrei _______________________________________________ fprint mailing list [email protected] http://lists.reactivated.net/mailman/listinfo/fprint
