image in database
-
the user have to put his finger on the fingerprint scanner.....
-
lol....kid...its a project..and yeah i have used name of facebook and gmail as a example.....and i have already told...that i have to do interfacing of electronic with server.......:mad:
if u don't have knowledge about this..then don't reply...
-
And how will he do that if the scanner is connected to the server, and the user is at home?
ook....as i have told u its a project...and it has wide variety of applications in industries and MNCs...........and yeah i just want to show that this can be implemented..... and yeah the finger print scanner will be with the user(as in case of dell laptops..there is a fingerprint scanner)...and then with the help of that scanner ..scanned image can be given to the server....(and i think this can be done with the help of socket programming)...
-
vinay dahiya wrote:
if u don't have knowledge about this..then don't reply..
Statements like this are considered abusive on this site. Please remove it.
he has also used statements like this......" bastard programmer from the hell"... i think u should see that statement also...
-
lol....kid...its a project..and yeah i have used name of facebook and gmail as a example.....and i have already told...that i have to do interfacing of electronic with server.......:mad:
if u don't have knowledge about this..then don't reply...
vinay dahiya wrote:
lol....kid..
Thanks for the compliment :D It is a request that comes rather often on this forum, usually from an academic circle. From a webapplication you will not have direct access to the users' hardware. Good luck btw.
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^][](X-Clacks-Overhead: GNU Terry Pratchett)
-
he has also used statements like this......" bastard programmer from the hell"... i think u should see that statement also...
-
he has also used statements like this......" bastard programmer from the hell"... i think u should see that statement also...
-
vinay dahiya wrote:
lol....kid..
Thanks for the compliment :D It is a request that comes rather often on this forum, usually from an academic circle. From a webapplication you will not have direct access to the users' hardware. Good luck btw.
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^][](X-Clacks-Overhead: GNU Terry Pratchett)
:) but will u tell me..that can't i access the ports of pc and then i can take input from the port(using socket programming)..and then that input can be given to the server.......
-
:) but will u tell me..that can't i access the ports of pc and then i can take input from the port(using socket programming)..and then that input can be given to the server.......
-
so what should i do now.....????
-
so what should i do now.....????
Verify that the technical limitation I named actually exists, then find a workaround or an alternative. Better yet, make a list, naming merits and expected problems for each; make prototypes of the best two ideas. To get you started; you could opt to write a browser-addin (for each type of browser you want to support) that acts as an intermediate, or, you'd write a client-side application (think WinForms/WPF) that provides the same functionality. The latter will sound like a bad idea to your professor; then again, it would not only be the correct approach; you'd end up with a finger-print protected password-manager. Would not require a dedicated server, as it could run completely (!) on the client. There's no risk in me loosing data, as all my sensitive data never has to leave the client-machine. And best of all, you wouldn't need Google's cooperation to provide the functionality and being able to claim to support GMail. If you take the latter approach, then you might also want to look up the strategy-pattern. It would be nice if the password-manager also supports other ways of authenticating/authorizing. That would be targetting a shrinkwrap-application. If your course requires you to write an enterprise-level application, you'd need the first approach.
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^][](X-Clacks-Overhead: GNU Terry Pratchett)
-
Verify that the technical limitation I named actually exists, then find a workaround or an alternative. Better yet, make a list, naming merits and expected problems for each; make prototypes of the best two ideas. To get you started; you could opt to write a browser-addin (for each type of browser you want to support) that acts as an intermediate, or, you'd write a client-side application (think WinForms/WPF) that provides the same functionality. The latter will sound like a bad idea to your professor; then again, it would not only be the correct approach; you'd end up with a finger-print protected password-manager. Would not require a dedicated server, as it could run completely (!) on the client. There's no risk in me loosing data, as all my sensitive data never has to leave the client-machine. And best of all, you wouldn't need Google's cooperation to provide the functionality and being able to claim to support GMail. If you take the latter approach, then you might also want to look up the strategy-pattern. It would be nice if the password-manager also supports other ways of authenticating/authorizing. That would be targetting a shrinkwrap-application. If your course requires you to write an enterprise-level application, you'd need the first approach.
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^][](X-Clacks-Overhead: GNU Terry Pratchett)
thnks....eddy....the all i have to do now...is to think upon some new concept....
-
thnks....eddy....the all i have to do now...is to think upon some new concept....