| Summary: | Seperate signals about stun servers and relayinfo changes | ||
|---|---|---|---|
| Product: | Telepathy | Reporter: | Sjoerd Simons <sjoerd> |
| Component: | tp-spec | Assignee: | Telepathy bugs list <telepathy-bugs> |
| Status: | RESOLVED FIXED | QA Contact: | Telepathy bugs list <telepathy-bugs> |
| Severity: | normal | ||
| Priority: | medium | ||
| Version: | unspecified | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | Call | ||
| i915 platform: | i915 features: | ||
Also we should improve the naming and documentation, from #24936:
> Stream.I.Media (also see updated smcv/call branch for some editorial fixes):
>
> * ServerInfoRetrieved and RetrievedServerInfo are ambiguous member names.
> Without looking at the spec, try to tell me which one is the signal and which
> one is the boolean property :-) Can we disambiguate these better?
>
> * It is claimed that STUNServers cannot change once the stream has been
> created. This seems likely to be a lie, given that we now have change
> notification of a sort? It should have proper change notification, though, if
> it can change (perhaps just an "added" signal).
>
> * Likewise, what is RelayInfo's change notification?
Fixed in git. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.
From #24936 > There probably should be separate signals for STUN servers and RelayInfo > changing.. And the signal should probably contain the relevant information > instead of having to do another round trip.