image in database
-
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....