The room names are case insensitive by JID rules (username and server
portions are case-insensitive). If ten people are in the room and all
joined with different cases in the name; one calling it room, another
calling it Room, another ROOM, etc. which one does the room use when
talking to its
hi,
> This could at least be considered correct behavior. What would you
> define correct behavior to be?
I'd just like the conference module to leave the name of the room like
I typed it :)
what is the interest of forcing the room names to be lowercased ?
regards,
Benoit.
--
Benoit Orihuela
This could at least be considered correct behavior. What would you
define correct behavior to be?
-David Waite
Benoit Orihuela wrote:
>hi,
>
>>The Jabberd process and/or the conference module sends all response with
>>the name converted to lowercase:
>>
>>NJ::Client: CallBack: sid(3BA14366) re
hi,
> The Jabberd process and/or the conference module sends all response with
> the name converted to lowercase:
>
> NJ::Client: CallBack: sid(3BA14366) received( to='[EMAIL PROTECTED]/ChatBot'
> from='[EMAIL PROTECTED]/chatbot
I don't know why but the room names are lowercased in the conferen
I've found an interesting behavior while setting up 'chatbot'. This is using
the more recent CVS code from jabber.org for all perl modules, for chatbot,
and for the 'conference' module.
While XML:Stream and Jabber::Client pass along conference names with
uppercase unchanged:
NJ::Client: SendXML
