Re: Bug fixing

The interesting thing about it is it does broadcast the users REAL JID
along with the mDNS information... It would basically show up as
"another way to reach" the same JID... one which might take precedence
over going out to the server.

>From what I understand, it does belong in Gabble. Gabble would just
publish it's connection's information in Avahi, and open a port to
listen to XMPP messages from those users. Those messages would be fed
into whatever existing code pipeline Gabble uses to track messages and
routed to client programs. They probably wouldn't even know. In routing
an outbound message, it would just check Avahi to see if anybody local
claims responsibility for the JID.

*ignoring big security problem that people locally could intercept
messages*

On Wed, 2006-07-26 at 19:14 +0100, Martyn Russell wrote:
> On Wed, 2006-07-26 at 18:54 +0100, Robert McQueen wrote:
> > Martyn Russell wrote:
> > > Mmm, this is an interesting one. I think this was recently fixed in
> > > Loudmouth IIRC. It should probably be done by each protocol backend or
> > > centrally in Telepathy somewhere either way, this should not be done in
> > > Gossip IMO.
> > 
> > Fixed? 
> 
> My mistake, I must have been thinking about something else.
> 
> > The mDNS link-local XMPP stuff is very different to normal XMPP
> > in use, you need to use mDNS queries to find people's presence, and
> > peer-to-peer XMPP-style connections to send messages. It's not even
> > clear to me that Gabble should do the zeroconf stuff, or if loudmouth
> > will be suitable for it without patching...
> 
> For those interested, this is the relevant bug for Gossip: 
> http://bugzilla.gnome.org/show_bug.cgi?id=325002
>