From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ie0-x231.google.com (mail-ie0-x231.google.com [IPv6:2607:f8b0:4001:c03::231]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 2436021F170 for ; Sun, 8 Sep 2013 15:57:01 -0700 (PDT) Received: by mail-ie0-f177.google.com with SMTP id qd12so1367007ieb.36 for ; Sun, 08 Sep 2013 15:57:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=WjP7Csi8/nKKWs+xlOgt5MSLfEVx8GY1P5rNNha04uY=; b=U/pTYayQbY1PivI9i3+ZVlxA6/gI8VNy3w1kcVW11KajQGxu6tD+W5549936dUNqsF vnCZ64lkBQSwi6DYCcD0E3jOxYwsgwWYN5Ey3K6jkCnpE6sTGqdCWSDGNQJ/sV711S70 dfgdnCarERQuTQZ5jp4nWkuWliBC+j6qaEuV8vwQsgWEpWs1zB8+jRxwbYO1AGo7kn4a Y46eC9/49jTpLd1j4ZDnbGuvstQFocVoWeErqfoas6hxucjCJE1LbDQ3mQw+nHDbNvI4 J/qcjtQ0LFQgpAxp+DCDnKU/4zdkdyIGEQrR2z0BAQeZdjCTNxhecQPTYVZGWywu0oS0 esXA== MIME-Version: 1.0 X-Received: by 10.50.20.99 with SMTP id m3mr5953715ige.54.1378681020215; Sun, 08 Sep 2013 15:57:00 -0700 (PDT) Received: by 10.64.231.35 with HTTP; Sun, 8 Sep 2013 15:57:00 -0700 (PDT) In-Reply-To: <522CF2D8.2050609@pocock.com.au> References: <522CCD9E.5040706@pocock.com.au> <20130908212355.GB14461@lists.bufferbloat.net> <522CF2D8.2050609@pocock.com.au> Date: Sun, 8 Sep 2013 15:57:00 -0700 Message-ID: From: Dave Taht To: Daniel Pocock Content-Type: multipart/alternative; boundary=047d7bd6b2b477fcda04e5e73020 Cc: "cerowrt-devel@lists.bufferbloat.net" Subject: Re: [Cerowrt-devel] Bringing asio to *WRT X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Sep 2013 22:57:01 -0000 --047d7bd6b2b477fcda04e5e73020 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable OK, well, I tossed it into ceropackages. it builds. It pulls in the boost headers for some reason. Is there some specific package on top of this for the webrtc stack you have package makefiles for? On Sun, Sep 8, 2013 at 2:57 PM, Daniel Pocock wrote: > > > On 08/09/13 23:23, Dave Taht wrote: > > On Sun, Sep 08, 2013 at 09:18:54PM +0200, Daniel Pocock wrote: > >> > >> > >> > >> Hi, > >> > >> I posted this contribution to OpenWRT but it has been ignored for almo= st > >> 12 months: > >> > >> > https://lists.openwrt.org/pipermail/openwrt-devel/2012-September/016771.h= tml > >> > >> I've tried asio on OpenWRT and it seems to work fine, I've submitted a > >> patch for it. Would it be possible to bring this directly into CeroWR= T? > > > > We maintain a packages repo (ceropackages-3.3) for various bits of > interesting > > stuff. > > > > Certainly a decent stun/turn server in the webrtc world would be > "interesting" > > The underlying asio library itself is general purpose - so it is not > just for STUN/TURN. TURN is very compelling now that WebRTC is taking > off and uses TURN by default from the browser. > > To give another example, asio has been used as a foundation for the > websocketpp suite, which enables both client and server websocket > development > > > It's not clear to me what else asio is - and if it is "decent enough"? > > > In general I am allergic to c++/boost stuff in tiny embedded systems - > we have > > only so much flash and ram to spare. What are the flash and memory > impacts? > > asio itself is a header library for asynchronous, event-based programming > > It comes in a boost version and a non-boost version. This is the > non-boost version, so it is likely to have less impact than the boost > version. I confess the full solution with SIP + TURN + SSL is a little > top heavy though, a device with 32MB RAM may not be enough, my WL-1043ND > couldn't handle it all. On the other hand, one of these jumbo routers > (I went and got a Buffalo WZR-HP-AG300H with 128MB RAM) is quite > suitable and can run a full WebRTC stack as a convenient alternative to > Skype. > > Here is a trivial asio example: > > > http://think-async.com/Asio/asio-1.4.8/src/examples/echo/async_tcp_echo_s= erver.cpp > > > Anyway, if you want to package it up I'll gladly fold it into > ceropackages, > > and build it, where more can fiddle with it. > > I've made up a patch against OpenWRT, to bring this into ceropackages do > I need to adapt the patch or you can easily use it as is? Please find > the Makefile attached. > > > > > > _______________________________________________ > Cerowrt-devel mailing list > Cerowrt-devel@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/cerowrt-devel > > --=20 Dave T=E4ht Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html --047d7bd6b2b477fcda04e5e73020 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
OK, well, I tossed it into ceropackages. it builds. It pul= ls in the boost headers for some reason. Is there some specific package on = top of this for the webrtc stack you have package makefiles for?


On Sun, Sep 8= , 2013 at 2:57 PM, Daniel Pocock <daniel@pocock.com.au> w= rote:


On 08/09/13 23:23, Dave Taht wrote:
> On Sun, Sep 08, 2013 at 09:18:54PM +0200, Daniel Pocock wrote:
>>
>>
>>
>> Hi,
>>
>> I posted this contribution to OpenWRT but it has been ignored for = almost
>> 12 months:
>>
>> https://lists.openwrt.org/pipermai= l/openwrt-devel/2012-September/016771.html
>>
>> I've tried asio on OpenWRT and it seems to work fine, I've= submitted a
>> patch for it. =A0Would it be possible to bring this directly into = CeroWRT?
>
> We maintain a packages repo (ceropackages-3.3) for various bits of int= eresting
> stuff.
>
> Certainly a decent stun/turn server in the webrtc world would be "= ;interesting"

The underlying asio library itself is general purpose - so it is not<= br> just for STUN/TURN. =A0TURN is very compelling now that WebRTC is taking off and uses TURN by default from the browser.

To give another example, asio has been used as a foundation for the
websocketpp suite, which enables both client and server websocket
development

> It's not clear to me what else asio is - and if it is "decent= enough"?

> In general I am allergic to c++/boost stuff in tiny embedded systems -= we have
> only so much flash and ram to spare. What are the flash and memory imp= acts?

asio itself is a header library for asynchronous, event-based program= ming

It comes in a boost version and a non-boost version. =A0This is the
non-boost version, so it is likely to have less impact than the boost
version. =A0I confess the full solution with SIP + TURN + SSL is a little top heavy though, a device with 32MB RAM may not be enough, my WL-1043ND couldn't handle it all. =A0On the other hand, one of these jumbo router= s
(I went and got a Buffalo WZR-HP-AG300H with 128MB RAM) is quite
suitable and can run a full WebRTC stack as a convenient alternative to
Skype.

Here is a trivial asio example:

http://think-async.com/Asio/asio-1.4.= 8/src/examples/echo/async_tcp_echo_server.cpp

> Anyway, if you want to package it up I'll gladly fold it into cero= packages,
> and build it, where more can fiddle with it.

I've made up a patch against OpenWRT, to bring this into ceropack= ages do
I need to adapt the patch or you can easily use it as is? =A0Please find the Makefile attached.





_______________________________________________
Cerowrt-devel mailing list
Cerowrt-devel@lists.= bufferbloat.net
https://lists.bufferbloat.net/listinfo/cerowrt-devel




--
Dave T=E4ht

= Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscrib= e.html=20
--047d7bd6b2b477fcda04e5e73020--