HTTP server

[daykin]

Hello,

Is the 'nullhttpd' component of this plugin still maintained? On our site-specific version, there is a patch from 2018 (before my time) that switched everything over to GNU Microhttpd instead. Thus, everything we've added (i.e. compatibility with newer FFMpeg versions) uses Microhttpd. I'm trying to gather information about the rationale for this switch.

[coretl]

I believe that nullhttpd was abandoned shortly after this was originally written, hence the copy of the nullhttpd source code into this repo. Does Microhttpd work on Windows too? If so then it sounds like an ideal replacement.

[daykin]

according to the project page, yes. Do you happen to have a Windows testing environment handy? I can send the patch over if so. Otherwise I can probably get one set up and check it out.

[coretl]

Do you happen to have a Windows testing environment handy?

Unfortunately not. Although I'm the original developer of this module, I've moved jobs since I wrote it, so it would be up to someone else to make and test the changes. I was just commenting as I know the history...

[MarkRivers]

I have a Windows test environment if you need me to test.

[daykin]

Thanks, Mark. Here is the patch:
microhttpd.patch

[MarkRivers]

@daykin can you do this as a pull-request?

[daykin]

Sure. #34

[MarkRivers]

Sorry, I forgot about this. The other merges I have done recently have broken #34. Can you merge the new master and update the PR?

[daykin]

No problem. Since Phoebus+PVAccess now supports compressed data, we aren't using this plugin anymore, however.