Toby Schaffer wrote: > I hope nobody minds me bringing up an older thread... Responding to > Nathan's original reply > <http://mail.jabber.org/pipermail/jdev/2008-June/026983.html> that this > should be handled as a MUC which the client could make transparent, I'm > hoping for something that requires no interaction from the user, not > even having to accept a MUC invitation.
Again, its quite possible for a client to do this. The protocol
(particularly with the <continue/> element) has the necessary bits and
parts to let the client know that it should be a seamless
transition...both on the initiating, and receiving side.
This is all client implementation issue.
> Ideally, the message would
> simply appear on the recipients' screens as if they were IM'd
> individually (except for the other recipients' JIDs, of course). Again,
> it seems that XEP-0033 addresses all this, and I'm surprised there are
> no implementations.
You are correct, though, in that you could use XEP-0033 capabilities to
do this as well...though I suspect you're going to find a lot more
interoperability corner cases when working with other clients that don't
support XEP-0033.
At least, with the MUC case, if you're interacting with a client that
doesn't provide that seamless user experience, it will "gracefully" fall
back to giving a MUC invite to the user to confirm. If you're
interacting with a client that doesn't support XEP-0033, your multi-way
flow of messages isn't going to work the way I think you want/expect it
to. (ie, you send a XEP-0033 message to two people; one of them, with a
non-XEP-0033 client, responds, and the message only comes to you, and
not also to the other user...correct me if I'm wrong on this).
I suspect this is why you haven't seen wide adoption of XEP-0033 as its
usefulness is largely dependent on other clients implementing it as
well...its the age-old bootstrapping problem.
--
Jeff McAdams
"They that can give up essential liberty to obtain a
little temporary safety deserve neither liberty nor safety."
-- Benjamin Franklin
signature.asc
Description: OpenPGP digital signature
_______________________________________________ JDev mailing list FAQ: http://www.jabber.org/discussion-lists/jdev-faq Forum: http://www.jabberforum.org/forumdisplay.php?f=20 Info: http://mail.jabber.org/mailman/listinfo/jdev Unsubscribe: [EMAIL PROTECTED] _______________________________________________
