Bug 195224 - iChat / Bonjour / Rendevous/ Link-Local Messaging chat provider
Summary: iChat / Bonjour / Rendevous/ Link-Local Messaging chat provider
Status: RESOLVED FIXED
Alias: None
Product: ECF
Classification: RT
Component: ecf.providers (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: ecf.core-inbox CLA
QA Contact:
URL: http://www.xmpp.org/extensions/xep-01...
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2007-07-03 03:31 EDT by Max Berger CLA
Modified: 2015-11-19 17:22 EST (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Max Berger CLA 2007-07-03 03:31:11 EDT
It would be really nice if ECF had support for the iChat (aka link-local messaging, or XEP 174) protocol. It already uses jmdns for multicast discovery, and supports xmpp, so this can't really be too far off.
Comment 1 Scott Lewis CLA 2007-07-22 20:21:26 EDT
ECF does support bonjour/rendevous now (discovery API implementation), and XMPP as well.  If I'm not reading the XEP 174 incorrectly, I think that creating a service ID with type "_presence._tcp.local." with the discovery API would essentially do the trick.  Max is this what you are looking for?

I'm adding helpwanted to the keywords, as although this would be/is very cool I'm not sure whether we'll have resources to address immediately.
Comment 2 Remy Suen CLA 2007-07-22 21:36:31 EDT
Marking as 'helpwanted'.
Comment 3 Max Berger CLA 2007-07-25 08:46:04 EDT
Yes, I do believe this is what I am looking for. Unfortunately I have no actual implementation experience with XEP 174, but AFAIK this would make it iChat compatible (which is what I am looking for).

The things to be done here:
- advertise yourself as a service. For this a user should be able to specify a name to be used.
- listen to other advertisements, and display them as possible chatpartners.
- support sending messages to locally discovered partners, using the slightly modified local chat protocol.

I will, of course, volunteer to test. For the moment, I cannot volunteer implementation time, although this may change in the future.
Comment 4 Alex Blewitt CLA 2009-07-03 09:32:10 EDT
FYI with a Mac OS X iChat client, I get:

bigmac[~] dns-sd -B _presence
Browsing for _presence._tcp
Timestamp     A/R Flags if Domain                    Service Type              Instance Name
14:15:19.620  Add     2  4 local.                    _presence._tcp.           alex@bigmac-3

bigmac[~] dns-sd -L alex@bigmac-3 _presence._tcp. local.
Lookup alex@bigmac-3._presence._tcp..local.
14:15:58.667  alex@bigmac-3._presence._tcp.local. can be reached at bigmac-3.local.:49159
 txtvers=1 aim=alexanderblewitt port.p2pj=49159 status=avail 1st=Alex jid=alex.blewitt@gmail.com email=alex.blewitt@gmail.com  last=Blewitt AIM=alexanderblewitt vc=SDCURA!XN ext=5I phsh=c61a5df2c0f4e6addfaa6bbf69c60a5295c22860

The keys are described here:

http://xmpp.org/registrar/linklocal.html

The point is that the port (49159) should be a XMPP stream, which there's probably the APIs to already do, right? So this is just about setting up an ECF server/client that will do that. Unfortunately, I don't have enough ECF nous to know how to do this, but if there's a noddy ECF example (or test  case) that someone can point me in the direction of, as well as the way in which the ECF bonjour stuff works, I'll have a go.
Comment 5 Scott Lewis CLA 2015-11-19 17:22:16 EST
resolving as wontfix.  If resources become available to do this, please reopen.