On 22 January 2018 at 14:13, Evgeny Khramtsov <[email protected]> wrote: > Mon, 22 Jan 2018 13:42:59 +0000 > Dave Cridland <[email protected]> wrote: > >> I don't think RTTs should block UI either, but startup RTTs mean we >> cannot send or receive messages for several RTTs, and that's a very >> real problem over slower networks. > > What problem? If you're on slow network, expect everything to be > slow, because, well, the network is slow. >
Sure. But blocking RTTs at startup are a soluble problem here. Even with XEP-0198 resumption, there are currently something like 10 RTTs required Reducing the startup-RTTs can reduce the time-to-message from several seconds down to just a second or two. In mobile, average RTT is around 75ms on a decent 4G LTE session, so it's just a matter of reducing the time-to-first-message to the 300ms mark from a second or two. Not amazing, but it's worthwhile if we need it in other cases - I'd call it a "nice to have". >> From a more cynical standpoint, it also addresses a commonly held >> belief about XMPP (startup is really slow and it's really chatty!) >> without causing harm. > > I don't see this as a "commonly held belief". If you know how Web works, > you would never assume XMPP is slow. I don't remember anyone > complaining in my bugtracker about slow RTT. > That doesn't surprise me at all. The kinds of people who think XMPP has a particularly slow startup are generally those who aren't using XMPP, and are choosing something else. > To put it simply: I agree there can be use cases when you absolutely > need to work in a slow network (sending stanzas to the Moon and back, > as an example), and maybe there are indeed some problems with RTTs. But > I see this as a very narrow use case. So I would agree that the XEP will > be used by *some* software, and I'm fine with that. What bothers me is > that this may become a trend, seeing the XEP as a successor to the > "standard" approach, and even be put into "compliance suite". I understand your point. However, I think that while this is rarely a "must have", it is a "nice to have" across a much broader set of use cases. Dave. _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
