I find it awkward to pull out the cause of a disconnect on e.g. password failure. I've added a subclass of IOException that preserves the CONNACK code that caused the exception. Since an IOException is still thrown no changes are required in the callers.
I find it awkward to pull out the cause of a disconnect on e.g. password failure. I've added a subclass of IOException that preserves the CONNACK code that caused the exception. Since an IOException is still thrown no changes are required in the callers.