I am not using the slide client, only the slide server. And both 2.0 and the 2.1 versions are working fine.
/jacob ----- Original Message ----- From: <[EMAIL PROTECTED]> To: "Slide Users Mailing List" <[EMAIL PROTECTED]> Sent: Friday, July 30, 2004 4:52 PM Subject: Re: roles of users, users in a role again, ANY CLUE? > Hi jakob, how do you get this?? > I tried with the command line client, that returns nothing. > Frank > > What do you mean when you say group-member-set cannot be read! If I do a > > propfind on DAV:group-member-set then I get a list of users in a group. > > > > /jacob > > > > ----- Original Message ----- > > From: <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > Sent: Friday, July 30, 2004 9:55 AM > > Subject: roles of users, users in a role again, ANY CLUE? > > > > > >> Hi there again. > >> I already asked a question about this, but the answers where quite > >> unsatifying. > >> > >> I write a webfrontend to administrate the slide's (or any other) webdav > >> repository. Therefore I need to find out which roles include which > >> users, > >> or which user is in what role. It was sais, that the > >> "group-member-set"-Property of a role can only be set, but never read. > >> But > >> why? How should I work on this then?? > >> > >> There was the proposal, to store the content somewhere else, but this > >> does > >> just help, if the repository is ONLY accessed and worked on with my > >> frontend. But I wnat to be able to connect and work on any WebDAV > >> Repository, that I have permission to. And I also want to update > >> role-user > >> associations in alreday existing Repositories. > >> > >> And it is very important, that this happens via the webdav protocol and > >> not internaly by some source hack, because I can not internaly hack > >> other > >> peoples WebDAV-Repositories! > >> > >> Any ideas? Where does this strange restriction come from? Is it a bug? > >> > >> Regards, > >> Frank > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > >> For additional commands, e-mail: [EMAIL PROTECTED] > >> > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
