Thanks :) I do not have a strong opinion regarding the "need", it was more a way to explain what I was trying to achieve with that idea. I am working on a client library these days and I am trying to be widely compliant and try to adapt to the server policy regarding whitespace keep-alive. I can easily live with "best practices" instead of "standards" and hardcode a few values in my lib.
Cheers, -- Mickaël Rémond > On 11 Jun 2019, at 14:31, Guus der Kinderen <[email protected]> > wrote: > > I'd have to check, but I think we're sending a IQ Ping when the client misses > it's first white space ping interval (whatever we deem is appropriate in that > server config), and define the client to be disconnected when it doesn't > respond in a timely manner. This covers both of your "the client is being > silly" scenario's: to many whitespace pings aren't adding much overhead to > the server, while to few pings are covered by the IQ Ping. I agree with you > that it's all very unspecified, which could be improved on. I'm not seeing > much of a direct _need_ to do that, but I'd not oppose it either. > > On Tue, 11 Jun 2019 at 14:24, Mickaël Rémond <[email protected] > <mailto:[email protected]>> wrote: > Hello Guus, > >> On 11 Jun 2019, at 14:00, Guus der Kinderen <[email protected] >> <mailto:[email protected]>> wrote: >> >> What we need basically is a way to negotiate the interval with server >> >> I'm not sure if this is _needed_? Without this being a requirement, much of >> the complexity of "making this more standard" falls away. > > Well, I think if the server does not have to approve the value, client could > expect to set it to something extreme (like 1s) or useless (like 1 days). The > server could thus reply with a different value. And still the server needs to > know at which rate the client is expected to send the keep alive. > But, yes, it is always possible to do something like that in a non standard > way. My point was trying to agree on something to make life of client > developers easier :) > >> A server could, before determining that a connection is lost, attempt to >> send any IQ stanza (PING is an obvious choice, but any query will do). As >> the client is obliged to respond, if anything with an error, the server >> knows if the connection is, in fact, lost. > > What would be the trigger for determining that the connection is lost and > send the ping? Is it whitespace keep-alive or anything else? > > Thanks! > > -- > Mickaël Rémond > > _______________________________________________ > Standards mailing list > Info: https://mail.jabber.org/mailman/listinfo/standards > <https://mail.jabber.org/mailman/listinfo/standards> > Unsubscribe: [email protected] > <mailto:[email protected]> > _______________________________________________ > _______________________________________________ > Standards mailing list > Info: https://mail.jabber.org/mailman/listinfo/standards > Unsubscribe: [email protected] > _______________________________________________
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
