Perhaps we just need to code up a demo using this approach and probe
the challenge moot: I'd be thrilled if the building blocks we already
have solve this problem and be put in place immediately!
Chris
Sent by 1G iPhone.
On Jun 18, 2008, at 15:29, "Bob Wyman" <[EMAIL PROTECTED]> wrote:
Chris,
I can't see any reason why an XRDS file with a link to the
appropriate JID would NOT be the correct way to implement this. Is
there something I'm missing?
bob wyman
On Wed, Jun 18, 2008 at 2:58 PM, Chris Messina <[EMAIL PROTECTED]
> wrote:
Let me frame the challenge/opportunity this way:
Presume that I have a URL of my own, given a recipient URL, I want
to be able to send a message "at it" and have it be received on the
other end, and be routed properly, based on the recipient's rules.
As the sender, I just want to be able to send a message and know
that the recipient should receive it.
This parallels having a "from" email address and sending it "to" a
recipient email address. But in this case we're replacing email as
the identifier with a URL.
So if I self-identify as http://twitter.com/factoryjoe and I want to
send a message to http://twitter.com/redmonk, if on that endpoint is
a discovery document that suggests where to send messages and how to
sign them so that the messages will be received and not rejected
outright, I think we're getting somewhere.
I see no reason not to use ATOM or XMPP for this, except that XMPP
doesn't work well with today's shared hosting environments. Perhaps
we use XRDS discovery to point to an XMPP endpoint and then offer a
fallback ATOM endpoint in the case that XMPP would fail?
You know that I'm against inventing unnecessarily -- which is why I
pointed out this microblogging effort. It might not be the way to do
it, but it gives us an example of someone's thinking that's actually
been implemented and gives us something to build against.
Chris
