ObjXMPP  All files named "src/XMPPConnection.m"

There no longer is an Xcode project for which it is needed. file: [c3592e505e] check-in: [cd21ff1157] user: js, branch: trunk, size: 31896 [annotate] [blame] [check-ins using] [diff]

This disables the new automatic certificate verification and still does
the manual verification. file: [cd38c39db4] check-in: [d23ac2b580] user: js, branch: trunk, size: 30926 [annotate] [blame] [check-ins using] [diff]

The session feature has been deprecated as of RFC 6120.
Some servers still offer it for client compatibility, but
mark it as optional. Not negotiating it in this case
saves us a round trip file: [24f700eb94] check-in: [ad2e692fe7] user: florob@babelmonkeys.de, branch: trunk, size: 30789 [annotate] [blame] [check-ins using] [diff]

This implementation only counts incomming stanzas and
sends ACKs on request.
While basic this already allows servers to write
messages to offline storage that were sent to,
but never received by a client. file: [934072be7a] check-in: [a618f77f45] user: js, branch: trunk, size: 26853 [annotate] [blame] [check-ins using] [diff]

This is thanks to XMPPMulticastDelegate. file: [c67c2c3e37] check-in: [878cac8ce0] user: js, branch: trunk, size: 26449 [annotate] [blame] [check-ins using] [diff]

Throwing an exception there was strange. file: [4cfcab5b18] check-in: [aa0dc6e2b4] user: js, branch: trunk, size: 26378 [annotate] [blame] [check-ins using] [diff]

While RFC6120 allows and encourages sending data with the success
message it is also legal to send the same data as a challenge and
await an empty response. This rework honors that fact. file: [abf53f803c] check-in: [0aab2fde67] user: florob@babelmonkeys.de, branch: trunk, size: 23068 [annotate] [blame] [check-ins using] [diff]

We don't need to do that. In fact we had to do additional work. file: [4a47a74ef8] check-in: [991c7aeff2] user: florob@babelmonkeys.de, branch: trunk, size: 9858 [annotate] [blame] [check-ins using] [diff]

This adds the new base class XMPPAuthenticator and the derived
classes XMPPSCRAMAuth and XMPPPLAINAuth.
They are now used for authentication from within XMPPConnection.

Also adds XMPPAuthFailedException which is thrown in appropriate places. file: [b8bdaffc4b] check-in: [6a3b0a9988] user: florob@babelmonkeys.de, branch: trunk, size: 9140 [annotate] [blame] [check-ins using] [diff]

The username is not necessarily a nodepart, therefore SASLPrep is more
appropriate than Nodeprep which we had before. file: [2e30d4f8cc] check-in: [ea9006fa33] user: florob@babelmonkeys.de, branch: trunk, size: 6892 [annotate] [blame] [check-ins using] [diff]