Tree: 03af489423

master

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from '03af489423'

${ noResults }

Commit Graph

2 Commits (03af48942336087e2e29dc27e5c523f40398104d)

Author	SHA1	Message	Date
Jon Kristensen	6c7aa54ea4	Make the stream failure types more intuitive and clear ... StreamError has been renamed to StreamFailure, as it's neither an error or an exception, and since the term "stream error" is ambigous (it can also refer to the stream error element on the XMPP stream). Furthermore, XmppTLSError has been renamed to TLSFailure. The data types related to the above mentioned failures are now exported. We do no longer clutter the API with detailed error conditions such as StreamNotStreamElement. These kinds of conditions are such rare occurances, and details about them are better suited in the logging system (to be implemented soon). Stream failures can occur either when a `stream:error' first-level XML element is encountered, or if something unexpected happens in the stream. Currently, `StreamErrorFailure', `StreamEndFailure', and `StreamOtherFailure' are defined for these purposes, but additional exceptions can be added if that would be helpful for the developers. TLSFailure is moved to Types.hs and is now exported. Also temporarily removed findStreamErrors.	13 years ago
Philipp Balzarek	786b8cd487	unsplit picklers	14 years ago