| Summary: | Call: Transport property in Endpoint not well explained | ||
|---|---|---|---|
| Product: | Telepathy | Reporter: | Olivier Crête <olivier.crete> |
| Component: | tp-spec | Assignee: | Telepathy bugs list <telepathy-bugs> |
| Status: | RESOLVED FIXED | QA Contact: | Telepathy bugs list <telepathy-bugs> |
| Severity: | normal | ||
| Priority: | medium | Keywords: | patch |
| Version: | git master | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | Call, review+ with some small fixes | ||
| i915 platform: | i915 features: | ||
| Attachments: |
patch to add documentation
correct patch to add doc the right patch |
||
|
Description
Olivier Crête
2011-10-13 16:09:16 UTC
Actually, I think the Endpoint could have a different type than the Stream for the ICE->Rawudp fallback.. So we need to document that correctly. Created attachment 54432 [details] [review] patch to add documentation Here is a patch that makes it a bit clearer when the Transport oin the Stream and Endpoints can differ Created attachment 54433 [details] [review] correct patch to add doc oops, previous patch was invalid Created attachment 54434 [details] [review] the right patch also attach the right file... +1 Seems reasonable. Please fix up the indentation and ideally add some nice tp:value-ref'ing while you're at it. Done, odd indentation was due to tab-spaces mix.. oops ! commit 9485135a28310f16472ff79a889a2d697a83dd05 Author: Olivier Crête <olivier.crete@collabora.com> Date: Wed Dec 14 16:15:00 2011 -0500 Call.Stream.Endpoint: Document when the Endpoint and Stream Transports can d |
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.