On Wed, Jul 24, 2019, at 1:06 PM, Dan Jenkins wrote: > oh I dont think it should ever live on the same websocket as the ARI > because of that very reason. But I mean if it could do ARI websocket, > inbound and outbound tcp connections thats as flexible as you'll ever > get and _anyone_ could build modern applications via any means. > starting development using ARI websocket and then potentially moving to > inbound/outbound whenever you need to scale further using an ARI proxy > for example... > > I just dont want this feature to come out and then be un-usable for X > number of applications. Surely Asterisk needs to be the most flexible > it can be?
Rome wasn't built in a day. I think building a solid foundation that the various methods (inbound / outbound) can then be built on top of is good. Launching with one direction initially to get things flushed out, and then later adding other options is perfectly reasonable in my opinion - and can be done since we allow features to be added to release branches. -- Joshua C. Colp Digium - A Sangoma Company | Senior Software Developer 445 Jan Davis Drive NW - Huntsville, AL 35806 - US Check us out at: www.digium.com & www.asterisk.org -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
