On Thu Apr 29 17:35:21 2010, bear wrote:
That was one of my thoughts as I was reading your first
post/question
-- why not provide the source id (or url) and let clients who
require/want the Atom items to request it as needed if they don't
want
to send to the server the DISCO item to enable full Atom support
Well, of course, when you start to posit OMB-aware clients, then you
can largely ignore the entire problem, because you get to design
efficient ways of pushing the information out on change and request -
likely, these ways could be fed back into the wider XMPP world. So
profiles could - in principle - be handled via XEP-0154 (remember
that?) and so on.
> Right - but what about when clients are offline? Is it a case of
> last-known-state wins? The trouble being we're assuming the last
case will
> be the next - if you're alternating between Atom/XHTML-IM aware
client and
> a non-aware, maybe mobile, client, you'll be gettign precisely
the wrong
> behaviour.
I suspect that this is the root of why it's all included, well, that
and the fact that Twitter sends *everything*
Right, but - and here we'll pretend there exist clients which consume
Atom - the one case we can be confident about is when a user has
*never* been seen with a Atom-supporting client. In that instance,
there really is no point in sending the extra data in the vague hope
that some client will later come online which will use it.
(Of course, if the user's online, and doesn't have an Atom-supporting
client, we do indeed just use XEP-0115 and we're done).
Dave.
--
Dave Cridland - mailto:[email protected] - xmpp:[email protected]
- acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
- http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade
