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

[Nick Withers]

Understood - I'll post a new patch with a test case (thanks for being on top of such things!).

(Sorry about the formatting...)
________________________________________
From: Sebastian Huber <sebastian.huber at embedded-brains.de>
Sent: Wednesday, 3 December 2014 6:12 PM
To: Nick Withers
Cc: rtems-devel at rtems.org
Subject: Re: Add an --enable-httpd-websocket configure option to enable WebSocket in the Mongoose HTTP server

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.

--
Sebastian Huber, embedded brains GmbH

Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone   : +49 89 189 47 41-16
Fax     : +49 89 189 47 41-09
E-Mail  : sebastian.huber at embedded-brains.de
PGP     : Public key available on request.

Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.