powered by Jive Software

Connection Manager: Non LDH character blows connection attempt

i’'m still hoping to provoke some reaction, so I just keep on posting about the connection manager module and my experience with it:

The usage of non-ldh-characters for the CM-name (i.e. whitespaces or underscores) really blows a connection attempt. the server just responds with a closing tag “</stream:stream>” causing the MXParser to run into an exception which is quite a ugly way to detect an failed connection attempt (took me some time to identify what exactly went wrong). Is this a necessary limitation to CM-names or useless?