[JDEV] MUC and creating rooms

[David Sutton]

Hi Vinny,

  You simply need to send back the form with only the config field - the
  parser will simply use default values for the rest of the fields. As
  soon as I rework the form parser, you will be able to simply send back
  an empty form.

  For reference, since you may wonder about this, if a groupchat client
  connects, the service automatically uses the defaults. The user still
  has the ability to modify, but would have to do it via raw xml, or
  reconnect with a compliant client.

Regards,

  David

On Fri, Jan 03, 2003 at 10:03:46AM -0500, Vincent Dibartolo wrote:
>    David,
> 
>            Thanks for the quick response.  Is there any way to
>    automatically create the room in a one-step process such that it will
>    assume the default settings?  On a side note, a confusing aspect of
>    the exchange is that some of the actual XML that I receive back when
>    creating a room has the phrase "To accept the default configuration,
>    click OK", which isn't exactly applicable to bots and other automated
>    scripts.  Thanks.
> 
>            -Vinny
> 
>    -----Original Message-----
>    From: David Sutton [mailto:jabber at dsutton.legend.uk.com]
>    Sent: Friday, January 03, 2003 12:34 AM
>    To: jdev at jabber.org
>    Subject: Re: [JDEV] MUC and creating rooms
> 
>    Hi there,
> 
>      Ok, its only one field that its really looking for, and its the
>    config
>      field. This was originally used when the service could receive a
>      number of different x:data forms, and I needed a simple way to
>      differiciate between them. I'm currently working on removing the
>      dependancy in the CVS version, so that an empty form will suffice.
> 
>    Regards,
> 
>      David

-- 
David Sutton
Email: dsutton at legend.co.uk
Jabber: peregrine at legend.net.uk
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 232 bytes
Desc: not available
URL: <https://www.jabber.org/jdev/attachments/20030103/d35f080b/attachment-0002.pgp>