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

[Nick Withers]

On Wed, 2014-12-03 at 08:12 +0100, Sebastian Huber wrote:
> On 03/12/14 08:05, Nick Withers wrote:
> > 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?
> 
> Ok, I think then we should first enable this unconditionally.  If 
> someone has code size problems, then we can start with a configure 
> option, but this is only a future optimization.
> 
> This new feature should have a test case in the existing test.

How's the attached?
-- 
Nick Withers

Embedded Systems Programmer
Department of Nuclear Physics, Research School of Physics and Engineering
The Australian National University (CRICOS: 00120C)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mghttpd-WebSocket.patch
Type: text/x-patch
Size: 8582 bytes
Desc: not available
URL: <http://lists.rtems.org/pipermail/devel/attachments/20141210/6cf7f7b0/attachment-0002.bin>