Bug 37662

Summary: Call: Have a wait to delay accepting a Content until resources have been acquired
Product: Telepathy Reporter: Olivier Crête <olivier.crete>
Component: tp-specAssignee: Telepathy bugs list <telepathy-bugs>
Status: RESOLVED WONTFIX QA Contact: Telepathy bugs list <telepathy-bugs>
Severity: normal    
Priority: medium CC: david.laban
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard: Call
i915 platform: i915 features:

Description Olivier Crête 2011-05-27 06:29:49 UTC 
On some platforms, you have a system that you can use to acquire a resource (like access to the camera or DSP). It may be need to wait until other applications have let it go before proceeding. We should have something in Call to not send the "content-accept" or "200 OK" for that specific content before these resources are acquired. At least in StreamedMedia, I don't see any way to do that and I don't think there is anything like that in Call either.

This could also be useful for preconditions to SIP calls (for VoLTE). But for VoLTE it would be for the whole channel, I would like to have it per-content too.
Comment 1 David Laban 2011-06-30 15:22:21 UTC 
I don't understand the use-case for this bug well enough. Please propose an API and I will take a look. Otherwise, there are a thousand ways to hack around it (e.g. don't let the ICE machinery progress to fully-connected or something).
Comment 2 Olivier Crête 2011-06-30 18:29:52 UTC 
In the streamhandler API we delay the "Ready" call.. I guess we could just delay the first GetAll call in tp-fs...
Comment 3 Olivier Crête 2011-11-09 16:23:36 UTC 
The other use-case for this is in VoLTE systems, you want to reserve network resources before you start processing the media of a Call.
Comment 4 Olivier Crête 2012-02-15 06:26:47 UTC 
Lets just do this client-side (in tp-fs).. by just ignoring the content/stream until we have the resources.

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.