Re: [Cerowrt-devel] Bringing asio to *WRT

[Dave Taht <dave.taht@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 2937 bytes --]

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 <daniel@pocock.com.au> 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 almost
> >> 12 months:
> >>
> >>
> https://lists.openwrt.org/pipermail/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.  Would it be possible to bring this directly into CeroWRT?
> >
> > 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_server.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
>
>


-- 
Dave Täht

Fixing bufferbloat with cerowrt:
http://www.teklibre.com/cerowrt/subscribe.html

[-- Attachment #2: Type: text/html, Size: 4033 bytes --]