On 4/30/10 10:51 AM, Bruce Campbell wrote: > On Fri, 30 Apr 2010, Jonathan Schleifer wrote: > >> I only had a short look at it now in the bus, but after that short >> read, it seems like my phone would ring every time I get a message, >> even though there's another resource where I actually read the message? > > Assuming your phone opted in to it (3.2), and hasn't opted out again (3.3).
Right. Carbons is an opt-in thing. If your mobile client doesn't opt in, it won't receive those messages. >> If I understood it right, it's missing some way to tell the other >> resources that you "accepted" a converstaion and are having it on this >> resource. For Carbon-ated clients, what is the use case for that behavior? > Not directly, but 3.8 (Avoiding carbons for a single message) indicates > a way for an individual message to not be copied to all other resources > of the sending and receiving parties. Rinse and repeat for each message > in the not-to-be-copied part of the conversation. Correct. >> It should also be possible to release a conversation again so that all >> resources receive it - for example if the window is closed or there >> was no message for a specified amount of time. There's no reason to release conversations if you don't take them in the first place. > Presumably clients that add <private xmlns="urn:xmpp:carbons:0"/> to > their messages would be prepared to cope with the other private resource > going away? Sure. Peter -- Peter Saint-Andre https://stpeter.im/
smime.p7s
Description: S/MIME Cryptographic Signature
