Hi Nick rtems-devel,
I could've sworn I needed the struct mg_connection declaration even to
just declare a function with its argument - but just to verify I tried
it again and I'm fine. So, for now, I'm retracting the patch.
Thanks for the tip!
On Thu, Nov 20, 2014 at 2:15 AM, Nick Withers
The attached patch is a proposed solution to a problem I am having with
interfacing with the mongoose httpd for which I've found no canonical (or
any other) clean solution.
The problem is that some of the data structures needed for some operations,
specifically writing callbacks that get invoked
Hi Ben,
Due to the license change, we can consider our version of Mongoose as
RTEMS Project maintained for now. I don't know if anyone is
maintaining a fork with an appropriate license.
Moving the struct definitions to the header file is sensible, although
the usual caveat is that users might
On 11/19/2014 1:24 PM, Gedare Bloom wrote:
Hi Ben,
Due to the license change, we can consider our version of Mongoose as
RTEMS Project maintained for now. I don't know if anyone is
maintaining a fork with an appropriate license.
There is a fork with the appropriate license.
On Wed, Nov 19, 2014 at 3:07 PM, Joel Sherrill
joel.sherr...@oarcorp.com wrote:
Just to be clear, I approve Ben's patch with mg_ prefix. :)
But long term, I want to see us consider moving the TCP/IP
to an external package so we can have IPV4, IPV4/V6, and
LWIP as options. Then layer various
On Wed, 2014-11-19 at 19:16 +0100, Ben Gras wrote:
The attached patch is a proposed solution to a problem I am having
with interfacing with the mongoose httpd for which I've found no
canonical (or any other) clean solution.
The problem is that some of the data structures needed for some
