On 03/17/2011 11:42 PM, Matthew Wild wrote: Hi,
> Sorry, this dropped off the bottom of my inbox (you're lucky it's only > been 10 days, thank stpeter for reviving it). And also my excuses for the slow follow up. It didn't drop to the bottom of my inbox, but to the bottom of the urgent tasks to do... >> I believe the cleanest fix to XEP-0124 would be: >> - Clarify that BOSH errors and BOSH termination should be send on the >> most recent connection. >> - Clarify that on termination (by request or by error), the eldest >> connection should closed by sending just an empty body (without >> 'terminate'). >> - Clarify that if there is any payload included in the terminate >> request, the payload should not need any response from the service. >> > > Minus not sending 'terminate', I agree with your points. OK. we can live with sending the 'terminate' on all responses. > Though on the > last one - I think it should be *allowed* to send stanzas that > generate replies, I see no harm in including such replies in response > to existing open requests or the terminate request. Of course if the > stanza is to another entity than the user's server, a reply really > can't be expected. Indeed, you can't know for sure the connection manager is the one handling the responses. So it is not sure you will be able to include the response. Beside that, we need to take into account some people want to do strange things like using BOSH for sending JSON. I only don't know for sure if the spec most forbid sending a payload that requires a response or that we must keep it more open. best wishes, Winfried
