On 14-02-11 05:42 PM, Jeremy Lainé wrote: > > On 11 Feb 2014 21:21, Matthew Jordan <[email protected]> wrote: >> >>> Either this is by design, in which case it needs to be documented, or it's >>> an oversight, >>> in which case I'd be happy to fix it. >> >> I'd go with oversight. >> > > Thanks for your answer I will propose a patch in that case. > > I have a small problem though: the ast_websocket_write function takes its > payload as a char* instead of a const char* for no apparent reason, is it > acceptable to change this?
It should be fine to do that. The underlying code that gets called with it accepts a const value. Cheers, -- Joshua Colp Digium, Inc. | Senior Software Developer 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA 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
