rcollier wrote:
Devs are the only ones who can determine whether an exception is temporary or permanent based on the context in which their application is being used. We cannot make that decision for them, it will inevitably be wrong.
I believe it is possible to make sane default decissions on what is a temporary error and what not. Of course this decisions will not be correct in every use-case, that's why it's imporant not to enforce them. But I would guess that 90% (or so) of the Smack users will be happy with the default categorization and will profit because the library has taken another burden from them. And that's what a good library should do: Offload as much as generic code as possible from the user, and to come with sane defaults.
And the others, who need XY not to be/to be an temporary/permanent exception can easily overwrite the defaults or ignore them alltogether.