Fix link-local messaging to identify who an incoming connection is from

[datallah@…]

Currently for local-link messaging, incoming connections aren't cached.

This means when you reply to an incoming message, it creates another connection to the original client instead of using the connection the message was received on. For clients like Pidgin, this means that communication doesn't work correctly unless the Gajim user was the original initiator of the conversation because multiple connections from the same IP are not permitted.

I discussed this in the chat room with Asterix earlier today.

I've created a patch that finds out who has initiated an incoming connection by matching the connections origin to the address in the roster.

[datallah@…]

Patch to identify connection origin for correct connection caching & reuse

[asterix]

(In [8976]) cache incoming zeroconf connections. fixes #3561

[asterix]

(In [8977]) cache incoming zeroconf connections. fixes #3561