From: Daniel Caujolle-B. <seg...@cl...> - 2004-04-09 17:43:13
|
=2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Le vendredi 09 Avril 2004 19:28, Mattern Thibaut a =E9crit=A0: > Citation de Daniel Caujolle-Bert <seg...@cl...>: > >>-----BEGIN PGP SIGNED MESSAGE----- > >>Hash: SHA1 > >> > >>Le vendredi 09 Avril 2004 19:01, Mattern Thibaut a > >> > >>=E9crit=A0: > >>> Citation de Daniel Caujolle-Bert > >> > >><seg...@cl...>: > >>> > -----BEGIN PGP SIGNED MESSAGE----- > >>> > Hash: SHA1 > >>> > > >>> > Hi, > >>> > > >>> > Le vendredi 09 Avril 2004 16:01, Bastien Nocera a > >>> > > >>> > =E9crit=A0: > >>> > > On Fri, 2004-04-09 at 16:26, Daniel Caujolle-Bert > >>> > > >>> > wrote: > >>> > > > -----BEGIN PGP SIGNED MESSAGE----- > >>> > > > Hash: SHA1 > >>> > > > > >>> > > > Hi, > >>> > > > > >>> > > > Le vendredi 09 Avril 2004 13:56, Miguel Freitas > >> > >>a > >> > >>> > =E9crit : > >>> > > > > On Thu, 2004-04-08 at 18:47, Siggi Langauf > >> > >>wrote: > >>> > > > > > On Thu, 8 Apr 2004, Mattern Thibaut wrote: > >>> > > > > > > >>> > > > > > [...] > >>> > > > > > > >>> > > > > > > copy domain + "/" + user -> user > >> > >>param > >> > >>> > > > > > [...] > >>> > > > > > > >>> > > > > > > split returned user into domain, user > >> > >>using > >> > >>> > "/" as separator > >>> > > >>> > > > > > That doesn't work if the user name contains > >> > >>"/". > >> > >>> > > > > > Additionally, it's just ugly. > >>> > > > > > >>> > > > > I agree with Siggi. > >>> > > > > > >>> > > > > I vote for heavily borrowing ideas from gnome > >>> > > >>> > folks, and not > >>> > > >>> > > > > reinventing > >>> > > > > >>> > > > Well, the thing i really want to avoid here is > >> > >>such > >> > >>> > Gnome centric stuff. > >>> > > >>> > > > IMHO we need to implement a generic (read > >> > >>universal) > >> > >>> > feature, not a > >>> > > >>> > > > specific one. > >>> > > > >>> > > That also means that xine wouldn't need to be > >> > >>modified > >> > >>> > to handle a > >>> > > >>> > > possible native smb plugin. > >>> > > >>> > Currently, it doesn't exist, this is a fact, and > >> > >>domain > >> > >>> > is smb oriented, > >>> > isn't it? > >>> > >>> "domain" and "workgroup" are smb oriented. > >>> But other user management systems use a tree to locate > >> > >>users. I think a > >> > >>> "user location" field is needed, you can name it like > >> > >>you want (domain, > >> > >>> workgroup, OU, directory...). > >>> > >>> > So what next, fish:// (andships://). > >>> > >>> hmmm... > >>> > >>> > I mean, i > >>> > think we should > >>> > provide a G.E.N.E.R.I.C structure, so i think we > >> > >>should > >> > >>> > collect more auth > >>> > informations to know what is really needed. > >>> > Also, why no a chained sub-structure like > >>> > typedef struct auth_prop_s auth_prop_t; > >>> > typedef struct auth_prop_s { > >>> > char *prop_name; > >>> > char *prop_value; > >>> > auth_prop_t *next; > >>> > }; > >>> > >>> you end with something more complex than the gnome > >> > >>stuff. > >> > >> err, maybe i was really not clear, stop using the word > >>"gnome", understood ? > > no ;) > you told me you wanted something simple. > > >> more complex ? i'm not sure since 99% of the current > >>plugins will not use it, complex ? look: typedef struct { const char *uri; /* caller should set the pointer to the uri */ char username[255]; char password[255]; auth_prop_t *props; } xine_auth_t; is it so compilated ? (did you ever played with post process, as client=20 side ?) Cheers. =2D --=20 73's de Daniel "Der Schreckliche", F1RMB. -=3D- Daniel Caujolle-Bert -=3D- seg...@cl... -= =3D- -=3D- http://naboo.homelinux.org -=3D- =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQFAdvzKLToa6iW5KUsRAv8wAKCyOKGdDnX1k/6Uv21+APZ/vK9aPgCeMeR1 2HouciNk9mVZ8gYlOH9nM2A=3D =3DqOvq =2D----END PGP SIGNATURE----- |