https://bugs.gpodder.org/show_bug.cgi?id=778

Thomas Perl <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |ASSIGNED
                 CC|                            |[email protected]
         AssignedTo|[email protected]             |[email protected]
     Ever Confirmed|0                           |1

--- Comment #1 from Thomas Perl <[email protected]> 2010-01-11 19:51:34 GMT ---
Hilton: Great to see you wanting to help out :)

The my.gpodder.org client code is going to be using a new library soon, and as
we support not only GNOME-based Desktops, we would need a fallback method for
cases where gnome-keyring is not available or desired.

A simple class that provides a way of storing a (username, password) pair would
be enough. This class could then have a subclass that implements the storage
using SQLite and another subclass that uses gnome-keyring. Whenever
gnome-keyring is available, it is used, and if not, the SQLite-based backend is
used.

It would be nice if in addition to the mygpo password, passwords for podcasts
(that are identified by their URL) are also stored in this "password backend".

The implementation can basically be independent of the rest of gPodder, just
provide a way for gPodder to store and retrieve the username/password
combination. Ideally, this should be supported for both mygpo and also the
podcasts.

Python bindings for gnome-keyring exist already. I'm assigning this to you.
Please re-assign to me if you need help.

-- 
Configure bugmail: https://bugs.gpodder.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
_______________________________________________
gPodder-Bugs mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/gpodder-bugs

Reply via email to