<div dir="ltr"><br><div class="gmail_extra">Okay, so that is what I thought. The client wants to know about the<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
channel, so that said, why don't we allow a client to create a channel<br>
directly? Something like:<br>
<br>
$id=uuid.generate()<br>
<br>
POST /channels/$id/?endpoint...<br>
=> Returns 200 OK<br>
<br>
I don't know if that is an option or not, but I _think_ that gets<br>
around the issue of a two step process. Obviously you return error<br>
codes on failure.<br></blockquote><div><br></div><div>As I noted in my reply to David, this unfortunately breaks linkedid propagation.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
My only other question with the two step process, is how long does the<br>
channel live for? What happens if you don't use /run, or asterisk<br>
dies, etc. Seems like it adds more overhead to the application to now<br>
manage said channels.<br></blockquote><div><br></div><div>That's no different than the other resources you create. If you create a bridge, you have to destroy it. If you create a channel, and it never hangs up - you have to destroy it. It's no additional work.<br>
</div></div></div></div>