On Sat, Aug 29, 2009 at 2:11 PM, Brian Cully<[email protected]> wrote: > > The problem, I think, is that <service-unavailable/>, potentially > <remote-server-not-found/>, and maybe more might not make sense as type > "cancel" since they're frequently generated for transient errors (the > service is temporarily offline, as you say). I see two options off the top > of my head (which hasn't had its coffee yet): > > 1) Add transient versions of at least <service-unavailable/> with an > error of type "wait." To distinguish the permanent vs. transient conditions > a server would only need to know if it's configured to allow for that > component to connect although it might not be at the time (potentially > <recipient-unavailable/> would due here), or,
Yep, reviewing error conditions I think that ejabberd (the server I'm using) is sending a service-unavailable instead of recipient-unavailable which makes more sense. Opening a ticket... :) > 2) Have the server which handles the component save the messages > until the component connects, akin to offline delivery. I prefer 1), since the pubsub service may decide which is the best strategy for delivering items to temporary unavailable recipients, instead of relying on a spool where it has no control and where there are potential denials of service >> Another thing: I think that the option of delivering items via <iq/> >> has already been discussed many times, but I don't find any reference > > I don't remember seeing this. All I remember is retrieving items by > iq, which is described in XEP-0060 s6.4. Perhaps it was discussed in the summit ad Bruxelles, but since we were split in small groups on different topics I missed the discussion. The fact is that when you want reliable delivery it is much easier to rely on direct acks than waiting for possible errors. Since it is all an internal thing we're going with <iq/> delivery, I was just wondering if it makes sense to make it a standard delivery option in node configuration. bye -- Fabio Forno, Ph.D. Bluendo srl http://www.bluendo.com jabber id: [email protected]
