I don't get why the storing and handling of fingerprints should be done in the daemon? I extended the signal EnrollStatus to return the print data. Now to the hard task. to implement the IdentifyStart/Stop methods and sending all the print data over dbus and reconstructing the print data structs.
Don't you think this would be a much nicer solution? On Tue, Dec 9, 2008 at 3:01 PM, Bastien Nocera <[EMAIL PROTECTED]> wrote: > On Tue, 2008-12-09 at 14:45 +0100, Linus Färnstrand wrote: >> Yes now everything seems to be working. A million thanks to you Bastien! >> >> But I still have a problem. How can I get the fingerprint data? >> I need to store them in a database so I can identify a person. >> Is that not implemented in fprintd? > > No, that's not implemented. The easiest would be to write another > storage plugin for fprintd that uses your particular database, so that > others can enjoy that too. > > You can model it after the code in src/file_storage.[ch]. It would need > to be a separate .so file that you'd drop into > $(libdir)/fprintd/modules. > > There's probably some more work to be done on that storage module side, > but I'd rather have somebody write a first draft before changing that > API any further. > > Cheers > > _______________________________________________ fprint mailing list [email protected] http://lists.reactivated.net/mailman/listinfo/fprint
