On Oct 21, 2013, at 8:15 AM, Joshua Colp <jcolp at digium.com> wrote: > Paul Belanger wrote: >> For the sake consistency I'd like to see us pick one. I can go either >> way, but the more I think about it >> >> /indicate?name=answer >> /indicate?name=hold >> /indicate?name=busy >> >> would give us a cleaner API for channels. >> >> Thoughts? > > I agree that the hold stuff should go into indicate but I'm torn on moving answer there because having it separate makes the API more approachable by non-telephony developers. They probably don't know about indications and may not even ever need to. They do know what answer is though right off the bat. +1 > (That's personal preference, as I favor a balance of clean/approachable/logical when it comes to API design). -- David M. Lee Digium, Inc. | Software Developer 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA Check us out at: www.digium.com & www.asterisk.org
