[JDEV] MUC and jadc2s

[David Sutton]

Hi there,

  I remember this came up before but don't remember any resolution, so
  lets start with the basics:

  * Is the packet truncated or rewritten?

  * Is the split in the same place every time?

  * Do you have an example of both a c2s request and a jadc2s request?

  That will do for starters.

Regards,

  David

On Sat, Nov 16, 2002 at 01:38:16PM -0500, Paul Curtis wrote:
> "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
> jdev at jabber.org
> http://mailman.jabber.org/listinfo/jdev

-- 
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/20021116/9d745416/attachment-0002.pgp>