Hi Peter, hi Matt, ...
Matt Tucker schrieb am 2005-03-22 17:37:25:
You could use zero-configuration networking for the discovery:
To add to this thread, we already support multicast DNS (called
Rendezvous by Apple) in Jive Messenger (Open Source server at
http://www.jivesoftware.org).
May I
On 23 Mar 2005, at 0:31, Justin Karneges wrote:
On Tuesday 22 March 2005 05:31 pm, Julian Missig wrote:
On 22 Mar 2005, at 20:00, Justin Karneges wrote:
Ignoring how iChat may or may not do it, I figure the most
straightforward
answer would be to have the clients perform the xmpp-core s2s
protocol
On Tue, Mar 22, 2005 at 08:31:54PM -0500, Julian Missig wrote:
Honestly, I prefer iChat's approach. Clients already have client
libraries that speak the c2s protocol. You strip out some of the
login/auth stuff and just use c2s to one another. That requires a lot
less new implementation
On Wednesday 23 March 2005 06:27 am, Julian Missig wrote:
On 23 Mar 2005, at 0:31, Justin Karneges wrote:
3) stanzas need to indicate both the 'to' and the 'from' (since
either
workstation might have multiple users. yes, I think we should be
forward
thinking here).
Ok, this is
On 23 Mar 2005, at 16:00, Justin Karneges wrote:
On Wednesday 23 March 2005 06:27 am, Julian Missig wrote:
On 23 Mar 2005, at 0:31, Justin Karneges wrote:
3) stanzas need to indicate both the 'to' and the 'from' (since
either
workstation might have multiple users. yes, I think we should be
On Wednesday 23 March 2005 01:13 pm, Julian Missig wrote:
Yes, except that the iChat way of doing this makes a *lot* of sense.
I don't know how you're expecting to to distribute presence using DNS-
SD, but with iChat, the service it's advertising *is* the presence.
So this is sort of by
On 23 Mar 2005, at 16:47, Justin Karneges wrote:
On Wednesday 23 March 2005 01:13 pm, Julian Missig wrote:
Yes, except that the iChat way of doing this makes a *lot* of sense.
I don't know how you're expecting to to distribute presence using
DNS-
SD, but with iChat, the service it's advertising
On Wednesday 23 March 2005 02:07 pm, Julian Missig wrote:
I don't mean to be presumptuous or rude, but I really don't think
you've thought through DNS-SD and how peer-to-peer Jabber would work
with it nearly enough...
Probably not. I was just trying to see how much of our own protocol we
On 23 Mar 2005, at 18:33, Justin Karneges wrote:
On Wednesday 23 March 2005 02:07 pm, Julian Missig wrote:
I don't mean to be presumptuous or rude, but I really don't think
you've thought through DNS-SD and how peer-to-peer Jabber would work
with it nearly enough...
Probably not. I was just
Okay, I'm confused... am I to understand that the jabber protocol can
be implemented over UDP/TCP-multicast?? I can see now how it would
sort of work... is there a JEP on this??? I would assume that it would
follow something along these lines :
1) client broadcasts its presence (stream:stream
On 23 Mar 2005, at 19:13, Anthony Ortiz wrote:
Okay, I'm confused... am I to understand that the jabber protocol can
be implemented over UDP/TCP-multicast?? I can see now how it would
sort of work... is there a JEP on this??? I would assume that it would
follow something along these lines :
1)
I SEE!!! said the blind man to the deaf man...
That seems like an interesting idea, though I think the current jabber
protocol doesn't allow for this (am I right?) UDP/Multicast chatting
is old-school, but I had never thought of using xmpp over it. I'm
curious though... under this system, Jabber
There is no such thing as a JabberID in this system. JabberIDs are
[EMAIL PROTECTED], and depend upon having a server.
Identification in this system is dependent upon Multicast DNS and DNS-
SD, which is how you get the IPs to connect to, the machine names,
etc. All of that stuff is thus
On Thu, Mar 17, 2005 at 05:28:16PM -0800, Leonardo Galicia Jimenez wrote:
Hi everybody, my name is Leonardo and i am trying to implement a system
using jabber. In this system i program jabber client using java, but these
jabber clients work transparently to the user, each jabber client is
. service
name, which mirrors the XMPP DNS SRV entry.
Regards,
Matt
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Peter Saint-Andre
Sent: Tuesday, March 22, 2005 12:59 PM
To: Jabber software development list
Subject: Re: [jdev] discovery services
On Tue, Mar 22, 2005 at 05:37:25PM -0600, Matt Tucker wrote:
You could use zero-configuration networking for the discovery:
http://www.cisco.com/en/US/about/ac123/ac147/ac174/ac206/about
_cisco_ipj_archive_article09186a0080132b85.html
To add to this thread, we already support
On 22 Mar 2005, at 18:37, Matt Tucker wrote:
You could use zero-configuration networking for the discovery:
http://www.cisco.com/en/US/about/ac123/ac147/ac174/ac206/about
_cisco_ipj_archive_article09186a0080132b85.html
To add to this thread, we already support multicast DNS (called
Rendezvous by
On 22 Mar 2005, at 19:14, Julian Missig wrote:
On 22 Mar 2005, at 18:37, Matt Tucker wrote:
You could use zero-configuration networking for the discovery:
http://www.cisco.com/en/US/about/ac123/ac147/ac174/ac206/about
_cisco_ipj_archive_article09186a0080132b85.html
To add to this thread, we
On Tue, Mar 22, 2005 at 07:16:50PM -0500, Julian Missig wrote:
Why _xmpp-client if you're advertising an XMPP Server?
Oh nevermind. I see that stpeter registered xmpp-client and xmpp-
server, intending that xmpp-client be the service that XMPP Clients
connect *to* while xmpp-server be
On 22 Mar 2005, at 19:25, Peter Saint-Andre wrote:
On Tue, Mar 22, 2005 at 07:16:50PM -0500, Julian Missig wrote:
Why _xmpp-client if you're advertising an XMPP Server?
Oh nevermind. I see that stpeter registered xmpp-client and xmpp-
server, intending that xmpp-client be the service that XMPP
On Tuesday 22 March 2005 04:40 pm, Julian Missig wrote:
For an official form of something like iChat Rendezvous, we'd need to
define what exactly an XMPP client-client protocol should look
like, which pieces of XMPP are disallowed, and when TCP connections
should actually take place. All
On 22 Mar 2005, at 20:00, Justin Karneges wrote:
On Tuesday 22 March 2005 04:40 pm, Julian Missig wrote:
For an official form of something like iChat Rendezvous, we'd need to
define what exactly an XMPP client-client protocol should look
like, which pieces of XMPP are disallowed, and when TCP
On Tuesday 22 March 2005 05:31 pm, Julian Missig wrote:
On 22 Mar 2005, at 20:00, Justin Karneges wrote:
Ignoring how iChat may or may not do it, I figure the most
straightforward
answer would be to have the clients perform the xmpp-core s2s
protocol with
each other. JIDs become [EMAIL
23 matches
Mail list logo
