[JDEV] MUC and jadc2s

[Paul Curtis]

"Houston, we have a problem."

This problem occurs with the following:

The newest MUC from CVS
The newest jadc2s from CVS
Both Exodus (0.7.9.0) and tkabber (0.9.2b1)

When a server is using jadc2s and MUC, the initial "room configuration" form (x:data) is displayed by the client as incomplete. This has been verified on Linux (server) and Solaris (server).

When the server is reverted to "c2s", the form is displayed by the same clients correctly and complete. Client connections over SSL and non-SSL do not affect the problem. It is reproducible every, single time.

I have not examined the x:data sent from the server through jadc2s to the client to determine what is missing or incorrect.

This issue is a show stopper for large deployments of jabber to use MUC.

paul

_______________________________________________
jdev mailing list
[EMAIL PROTECTED]
http://mailman.jabber.org/listinfo/jdev