Slightly more clear peer address resolvement

[WyriHaximus]

This came up during a chat in a private channel where there was some confusion about how $peer was populated. This PR fixes that be returning an array() and pulling those into two variables again using list().

[clue]

Thank you for looking into this 👍 While I agree that the current solution is far from ideal, I'm not sure the suggested change actually improves this much.

However, I vote 👎 for this change simply because this is a BC break given the API is currently protected and this is (unfortunately) something consumers could potentially rely on.

[WyriHaximus]

@clue assigned the milestone v2.0.0 for now. Are they any other breaking changes you would like to see? I have two more weeks off, I'm sure I can spent some time on those 😄

[clue]

@WyriHaximus I don't see anything on the roadmap for this component at the moment, so I'm not sure a v2.0.0 is something that is due any time soon?

This component is lacking documentation, so perhaps that's also what caused some of the confusion for people trying to make sense of the internal parameters. It's my understanding that some consumer facing documentation both as part of the class hierarchy and the README would help here 👍

[WyriHaximus]

@clue correct, so I made the milestone for anything we might want to have in there.

I'll look into that 😄