----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviewboard.asterisk.org/r/3541/#review11908 -----------------------------------------------------------
The most terse description ever... :-) While the issue mentions it, one of the purposes of having a WebSocket client would be to allow (in the future) ARI to connect back to some external system, as opposed to acting as the Server. There's a lot of additional work that would have to be done to incorporate that - for example, allowing ARI to re-try periodically if the external system is not up; configuration; etc. - but this is a first step towards that. - Matt Jordan On May 15, 2014, 1:10 p.m., Kevin Harwell wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviewboard.asterisk.org/r/3541/ > ----------------------------------------------------------- > > (Updated May 15, 2014, 1:10 p.m.) > > > Review request for Asterisk Developers and Joshua Colp. > > > Bugs: ASTERISK-23742 > https://issues.asterisk.org/jira/browse/ASTERISK-23742 > > > Repository: Asterisk > > > Description > ------- > > Add client websocket capabilities to Asterisk. > > > Diffs > ----- > > trunk/tests/test_websocket_client.c PRE-CREATION > trunk/res/res_http_websocket.exports.in 413541 > trunk/res/res_http_websocket.c 413541 > trunk/main/http.c 413541 > trunk/include/asterisk/http_websocket.h 413541 > trunk/include/asterisk/http.h 413541 > > Diff: https://reviewboard.asterisk.org/r/3541/diff/ > > > Testing > ------- > > Created some unit tests. > > > Thanks, > > Kevin Harwell > >
-- _____________________________________________________________________ -- 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
