Re: Expectations for Grilo plugins that require passwords



On 30/08/2011 09:46, Juan A. Suarez Romero wrote:
> 
> I can figure out a couple of ways to afford this problem in your case:
> 
> a) When trying to access the share through browse(), return an error
> telling the share is password-protected. The application would get the
> error and launch a dialog asking for the user/password, and then
> relaunching the browse.
> 
> b) Implement the signaling system you're talking about in the DMAP
> plugin. That is, DMAP plugin can read the DNS-SD record and, if a
> password is required, launching a signal. Application would be listening
> this signal and showing a dialog to get the password.
> 
I feel like the two best solutions are a) or actually implementing that
signal in core, since they are more generic. b) sounds like the path to
inconsistent additional APIs in plugins. I don't think we want that.

Guij
> 
> Probably there are other issues we should fix, but roughly speaking,
> maybe we can try with some of above options.
> 
> 	J.A.
> 
> 
> _______________________________________________
> grilo-list mailing list
> grilo-list gnome org
> http://mail.gnome.org/mailman/listinfo/grilo-list
> 



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]