Changes between Version 20 and Version 21 of YumDBusAPI

timlau (IP:
02/21/11 14:43:37 (7 years ago)



  • YumDBusAPI

    v20 v21  
    4646 * We need to create some kind of context, so that different callers aren't speaking to a single instance. If you don't do this you have huge problems with auditing/etc. This probably means changes in core yum, so that we can have more than a single "backend" at once. 
    4747 * Needs to not be a giant single point of failure, so that if user X does a query FOO that isn't affected by user Y doing operation BAR (this is probably related to the previous problem ... and has problems when someone does a transaction). 
     48  * In the current code, I work with a Lock/Unlock so only the consumer there has the lock, will be able to perform any actions until the lock is released. Currently there is no automatic lock timeout, so if there user somehow don't releases the lock, then the daemon is locked. So some kind of automatic unlock & shutdown if no actions is being performed for a period of time. 
    4849 * Previous attempts have tied authorization to API calls (this is probably helped by DBus), but this is almost worthless where "install" is a single API call. One hacky solution is to have a stupid number of specific APIs like "install_firefox_plugin". There really needs to be a better way though (maybe DBus feature?) 
     50  * Authentication is a True/False case, All methods there changes the system should need root authentication, selected ones will work without authentication (currently only !GetVersion), but others readonly action could be candidates to no require authentication. The main issues is Lock and !UnLock, should it be possible to lock yum without authentication ? 
    5052= Examples =