Specified class - we've found it

It is a quite embarassing situation for a developer if users keep coming up with bugs producing pointless error messages without any good reason and without any obivous way to reproduce. So in this case you’re at a complete loss.

That’s just had been happening to us since the release of DC++ 0.791 as several people reported that they get the infamous ‘Specified class not found’ error message printed to the main chat when they tried to connect to specific hubs. This one is actually a socket error message and it can sign some host resolving problems. But those addresses that reportedly gave this message for the users have always worked for us.

We had a suspicion that this problem has to do with the new IPv6 code but it wasn’t the case afterall. Today it turned out that the problem is because of the new address parser that was improved to support IPv6 addresses. It does support them well but it apparently also became slightly more strict and doesn’t love whitespaces anymore…

So people out there, if you get this message connecting your favorite hub, go the properties of that favorite hub and check the beginning and the end of the hub address so it does not contain any spaces… It’s often happens that if you copy/paste the address from another application it contains spaces which – especially if it is at the end – is really hard to spot.

Adding spaces to the hub address box will of course be prevented in the next version as well as existing saved addresses with whitespaces in them will be correctly handled…  amen.