On 2/3/10 9:23 PM, Liam wrote: > Thinking more about this, I want... > > subscriber to ack to service the pubsub event message
XEP-0184. > service to retry to subscriber by a configurable method if no ack There are retry guidelines in XEP-0184, too. > service to report fail to publisher when retries spent for a specific > subscriber Something like bounce processing in mailing list software? I've heard that suggestion before, but we've not yet deemed it core enough to add to XEP-0060. > service to report done to publisher when all subscribers either acked or > failed So you basically want to build some transactional functionality on top of pubsub. Nothing wrong with that, but AFAICS there's no consensus yet to define those features in XEP-0060. That said, we could define fairly simple message formats for both the bounce notifications and delivery-complete notifications. Peter -- Peter Saint-Andre https://stpeter.im/
smime.p7s
Description: S/MIME Cryptographic Signature
