Add an --enable-httpd-websocket configure option to enable WebSocket in the Mongoose HTTP server

[Nick Withers]

On Wed, 2014-12-03 at 07:48 +0100, Sebastian Huber wrote:
> Hello Nick,
> 
> what is the benefit of providing this WebSocket stuff?

I personally use it to serve dynamic content to web clients. The
callback mechanism that Mongoose provides allows me to hook these
requests into my application and reply with whatever I like.

Without processes, CGI's out of the question (well, that's my
understanding - haven't looked at it for ages) and I'm not aware of
other viable alternatives...? Having the embedded-side constantly write
data to files so they could be statically served just wouldn't be
workable with this application.

Does that make sense? Perhaps I should shoot you off some examples of
where I use it?
-- 
Nick Withers

Embedded Systems Programmer
Department of Nuclear Physics, Research School of Physics and Engineering
The Australian National University (CRICOS: 00120C)

> On 03/12/14 07:10, Nick Withers wrote:
> > On Thu, 2014-01-02 at 10:45 +1100, Nick Withers wrote:
> >> On Thu, 2013-12-19 at 15:38 +1100, Nick Withers wrote:
> >>> Hi all,
> >>>
> >>> The attached patch adds an "--enable-httpd-websocket" configure option
> >>> to enable WebSocket (see http://www.websocket.org ,
> >>> http://en.wikipedia.org/wiki/WebSocket ) in the Mongoose HTTP server.
> >> In case it's preferred, the attached patch unconditionally enables
> >> WebSocket support in the Mongoose HTTP server.
> >>
> >> The (PowerPC) psim mghttpd01.exe goes from 5708594 B to 5736668 B with
> >> this change, an extra 28074 B.
> > Any thoughts on this one?
> >
> > I'll likely have to regenerate patches, but to enable building the
> > Mongoose HTTP server with WebSocket, would we prefer to:
> >    - Add an "--enable-httpd-websocket" configure option
> >    - Unconditionally enable the feature
> >    - Force the user to patch the RTEMS source?
> >
> > Cheers!