Re: [civetweb] Interface for setting stack size and scheduler options

2016-05-27 Thread Christian Mauderer
I updated the Interface (header) in my draft. Could you take a look at the improved version? https://github.com/c-mauderer/civetweb/compare/1e4a9ee...a6bea13 Please note: I only updated the interface not the implementation. I will do that as soon as we have agreed on the interface.

Re: [civetweb] Interface for setting stack size and scheduler options

2016-05-23 Thread Christian Mauderer
Am Sonntag, 22. Mai 2016 23:26:07 UTC+2 schrieb bel: > > > > On Sunday, May 22, 2016 at 11:04:44 AM UTC+2, Christian Mauderer wrote: >> >> >> I created a draft for a callback. It's not worked out and only thought as >> a basis for further discussions: >> >> >> https://github.com/c-mauderer/ci

Re: [civetweb] Interface for setting stack size and scheduler options

2016-05-22 Thread Christian Mauderer
To the question from Joe Mucchiello: I think the thread startup is more a toppic of the init_thread callback that has been added here: https://github.com/civetweb/civetweb/pull/304 This function gets called after the thread is started. Is this what you had in mind? To bel: I created a d

Re: [civetweb] Interface for setting stack size and scheduler options

2016-05-18 Thread Christian Mauderer
Am Dienstag, 17. Mai 2016 21:07:46 UTC+2 schrieb bel: > > > > On Tuesday, May 17, 2016 at 7:50:02 AM UTC+2, Christian Mauderer wrote: >> >> >> The solution with the *start_thread* callback is quite a different >> approach than my original one but it looks like a quite portable solution. >> >> Am

Re: [civetweb] Interface for setting stack size and scheduler options

2016-05-16 Thread Christian Mauderer
At first: Sorry that I didn't react for such a long time. I just didn't find the time for working on that problem. I had some lengthy discussion on the RTEMS mailing list regarding the update to civetweb (or to be exact: where to put it) without a final solution. Therefore the update is current

Re: [civetweb] Interface for setting stack size and scheduler options

2016-05-03 Thread Christian Mauderer
Am 02.05.2016 um 20:35 schrieb bel: > > > On Monday, May 2, 2016 at 10:39:13 AM UTC+2, Christian Mauderer wrote: >> I agree that eventually not all variations have to be tested. It's only >> a challange to identify the irrelevant ones. >> >> Does the Travic CI allow to exclude certain combinatio

Re: [civetweb] Interface for setting stack size and scheduler options

2016-05-02 Thread Christian Mauderer
Am 27.04.2016 um 23:44 schrieb bel: > > > What do you think of the solution of ignoring parameters? > > > Ignoring parameters on a certain platform feels like > "Error: parameter xyz does not work on platform ..." > > If the parameter exists, it is supposed to work. > > > > Or a

Re: [civetweb] Interface for setting stack size and scheduler options

2016-04-27 Thread Christian Mauderer
I've got some feedback on the RTEMS mailinglist (part of https://lists.rtems.org/pipermail/devel/2016-April/014729.html): Am 27.04.2016 um 02:07 schrieb Chris Johns: >> I already contacted the civetweb author regarding two of the patches. >> One was a new one (civetweb now uses a timegm function

Re: [civetweb] Interface for setting stack size and scheduler options

2016-04-20 Thread Christian Mauderer
Hello, I'm currently try to replace our mongoose port with a current version of civetweb. Civetweb is a fork of the last MIT licensed version of mongoose that is still maintained under the MIT license. To reduce the number of patches that are necessary, I tried to clean up the patch that allows s