Vieri,

Thank you, I have committed you patch.

How do you think is it a good decision to allow users set the room id they
want to enter?

The problem is that room ids are internal info of Openmeetings and simple
users do not know it. They know just the name of a needed room but not its
database id. Only administrators of the Openmeetings server can see the ids.

So, what is the general scenario of this plugin using from your point of
view?

Best regards,
German Grekhov.



2012/8/9 Vieri <[email protected]>

> Hi,
>
> Done:
> https://issues.apache.org/jira/browse/OPENMEETINGS-399
>
> Thanks,
>
> Vieri
>
> --- On Thu, 8/9/12, [email protected] <[email protected]> wrote:
>
> > Hi Vieri,
> >
> > there was no patch file attached to your email.
> > I think it is not possible to attached files to emails via
> > mailing list.
> > Best would be to create a new issue at:
> > https://issues.apache.org/jira/browse/OPENMEETINGS
> > and attach a file. We will assign it to a dev and commit it
> > to our SVN then.
> >
> > Thanks!
> > Sebastian
> >
> > 2012/8/7 Vieri <[email protected]>:
> > > Hi,
> > >
> > > I'm attaching several patches for the Jitsi
> > OpenMeetings plugin (against SVN r1370136).
> > >
> > > New features:
> > > - enables provisioning properties
> > > - allows the user to force/set conference room ID
> > instead of getting an available room
> > > - allows the user to set a "display name" instead of
> > the SOAP login user name (in conjunction with provisioning
> > it can be easy to set useful "display names" based on one or
> > more parameters such as client IP/MAC address, "username"
> > provided to Jitsi, corporate database lookup or even LDAP,
> > etc.)
> > > - SOAP password is stored and loaded via
> > net.java.sip.communicator.service.credentialsstorage
> > >
> > > Fixes:
> > > - adapts to libjitsi/jitsi
> > > - createInvitationUrl should not hardcode
> > "openmeetings" in the invitation URL
> > > - property names changed from plugin.openmeetings.* to
> > net.java.sip.communicator.plugin.openmeetings.* (for
> > coherency)
> > > - displays Jabber chat window only when invitation URL
> > has correctly been generated
> > > - handles a null exception when no rooms are available
> > in openmeetings
> > >
> > > New properties for resources.properties (not included
> > in attached patches):
> > >
> > > plugin.openmeetings.DISPLAYED_NAME=Displayed name
> > > plugin.openmeetings.ROOM_ID=Room ID
> > >
> > > Sample PHP provisioning script:
> > >
> > > echo
> > "net.java.sip.communicator.plugin.openmeetings=\${null}\n";
> > > echo
> > "net.java.sip.communicator.plugin.openmeetings.DISABLED=false\n";
> > > echo
> > "net.java.sip.communicator.plugin.openmeetings.DISPLAYED_NAME=My
> > full name\n";
> > > echo
> > "net.java.sip.communicator.plugin.openmeetings.SERVER=
> openmeetings.mydomain.org\\:5080\n";
> > > echo
> >
> "net.java.sip.communicator.plugin.openmeetings.PROTOCOL_PREFIX=http\\://\n";
> > > echo
> >
> "net.java.sip.communicator.plugin.openmeetings.OM_URI_CONTEXT=/webmeetings/\n";
> > > echo
> > "net.java.sip.communicator.plugin.openmeetings.LOGIN=SOAPusername\n";
> > > echo
> > "net.java.sip.communicator.plugin.openmeetings.PASSWORD=thisIsAsecret\n";
> > > echo
> > "net.java.sip.communicator.plugin.openmeetings.ROOM_ID=3\n";
> > >
> > > Hopefully the code can be improved, merged into the
> > official tree and be useful to others.
> > >
> > > Vieri
> >
> >
> >
> > --
> > Sebastian Wagner
> > https://twitter.com/#!/dead_lock
> > http://www.webbase-design.de
> > http://www.wagner-sebastian.com
> > [email protected]
> >
>

Reply via email to