As a follow up to #25 I noticed that no matter what throwConnectionExceptions was set to, Laravel still threw one, so this fixed that.
Specifically to Laravel, the trigger_error call will stop execution, meaning even with throwConnectionExceptions switched off, any issue sending the packet will still trigger a full shutdown of the framework.
I'm not sure how best to adjust this behaviour without affecting non Laravel users.
As a follow up to #25 I noticed that no matter what
throwConnectionExceptions
was set to, Laravel still threw one, so this fixed that.Specifically to Laravel, the
trigger_error
call will stop execution, meaning even withthrowConnectionExceptions
switched off, any issue sending the packet will still trigger a full shutdown of the framework.I'm not sure how best to adjust this behaviour without affecting non Laravel users.