[Standards-JIG] JEP-0045 config field names
stpeter at jabber.org
Thu May 4 21:55:48 UTC 2006
-----BEGIN PGP SIGNED MESSAGE-----
Heiner Wolf wrote:
> in JEP-0045 I read in the configuration form example: <field
> label='Make Room Moderated?' type='boolean'
> var='muc#roomconfig_moderatedroom'> <value>0</value> </field>
> The var used to be var='muc#owner_moderatedroom'. ejabberd's MUC
> sends and expects var='moderated'.
> I understand that the var name is the service's choice. Is this
> This is ok as long as a natural or artificial intelligence looks at
> the label text and clicks the thing in a form. But if a client wants
> to set the value without presenting a form, then it must know the
> name. My client tries to set the 'Make Room Moderated' state
> programmatically. I don't know which var name to use. Depends on the
> MUC. I have to find out the MUC version and guess from that the
> variable name, which could change with any version. This is not good.
> Would it be possible to standardize in JEP-0045 a set of frequently
> used vars for MUC?
They already are standardized:
IMHO ejabberd has a bug here (the configuration variable is *not*
I apologize for the change in variable names a while back (no more
"muc#owner_*") but we discussed this on the list and I think the
consensus was not to go back.
Jabber Software Foundation
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 3641 bytes
Desc: S/MIME Cryptographic Signature
More information about the Standards