On Friday, 10 June 2022 at 08:02:16 UTC, Rob T wrote:
> Yeah last I remember Vibe was being re-coded to work like a library rather than only as an http server, like I said it was a long time ago when I was looking around at Vibe.

Oh, its weird static constructor thing it used to do.


> I'll also take a look at your library as well, this must be it https://code.dlang.org/packages/arsd-official%3Ahttp

That's my client, the server is in the cgi.d file,

https://code.dlang.org/packages/arsd-official%3Acgi

It does a LOT but I only documented some of it in there. I originally wrote it in 2008 to transition some PHP code over to D, then over the years it got more and more, including a full http server, websocket support, and some fancy code generator stuff in addition to the cgi, fastcgi, etc. interfaces. There's several benefits to following the old cgi architecture though including being able to scale up and down fairly easily so I still suggest people follow that style when using the embedded http server, but of course you can do things differently if you like just configure for threads or a smaller process pool, etc. Feel free to email me with questions.

Other modules in the arsd package offer other things I've needed over the years like database interfaces, a server-side DOM implementation, and then other things like gui application too too that isn't web related lol.

> A proxy however does come with a single point of failure issue, it would be more ideal for ipv6 enabled clients to by-pass the proxy and go directly to each container.

I've never tested ipv6 either. I'm sure not hard to add if needed, but my isp still doesn't support it anyway so it all useless to me! lol

On Tuesday, 7 June 2022 at 21:28:30 UTC, Paul wrote:
> However, one thing I miss from my PHP days (I know - script languages - Ugh), is having public comments below each manual page.

One thing I missed about php was going to like php.net/trim so i made my website dpldocs.info/strip etc. to bring it to D. My site there now runs its generator on dub packages too to help search across the ecosystem.

I need to clean some things up since I keep running out of disk space as there's 100 different versions of win32 needlessly copied etc. lol. I'm at 99% again so need to stop procrastinating at some point.

But once I do that, adding a comments field to each symbol would be technically pretty easy to do, I could even borrow some code from my beloved dwidder website and just paste it in!

The hard part would probably be spam control. The dwitter site makes you type a magic word (which it tells you on the page) and it seemed ok but it also isn't on search engines whereas the dpldocs.info site is, so that'd probably be different.

I'm of the opinion that most the comments should generally be in the docs themselves, and then you can submit via PR which means there's a review step and much less odds of spam bots hitting it. Also, as a user, reading through a bunch of random comments of varying quality just often feels bad; there's always a few gems of comments in there but looking through a bunch of lower quality ones is not as nice as the answer just plain being there. Comments would probably also be exempt from version checks meaning they can fall out of date. Of course, seeing the date on the comment gives people a clue it might be old.

Nevertheless, maybe I'll do it just as an experiment. Can always undo it later if it has more spam than value.

On Friday, 10 June 2022 at 12:00:02 UTC, Adam D Ruppe wrote:
> I've never tested ipv6 either. I'm sure not hard to add if needed, but my isp still doesn't support it anyway so it all useless to me! lol


As for ipv6, you should try to somehow get it working in your area if that is possible, it really does change how things are done, some of the old ways simply don't apply anymore, eg port forwarding, proxies, and even LAN firewalls do not make as much sense like they used to. My understanding is that all new infrastructure being rolled out for 5G networks and high speed switching do not even support ipv4 at all, although maybe as packets transported over ipv6, the general trend is to ditch ipv4 completely where ever possible.

BTW Thanks for the responses! It all sounds good and I will try out your library as well as vibe as soon as I can. I look forward to finally getting rid of the last of the C/C++ code that we have, it'll be one of those occasions where we will have a small celebration over it, no joke :)

On Friday, 10 June 2022 at 12:13:58 UTC, Adam D Ruppe wrote:
>
> The hard part would probably be spam control. The dwitter site makes you type a magic word (which it tells you on the page) and it seemed ok but it also isn't on search engines whereas the dpldocs.info site is, so that'd probably be different.
>
Maybe only forum users would be permitted to post comments against the manual? Then it would be no different than the control afforded by the forum we are chatting on now.

We may be surprised by how few people would have the courage to post anyway.

Regardless, I am thankful the group is at least considering it. It says a lot about how important D is to all of you. Let me know if there is anything I can do to help. If you feel it is appropriate and helpful, maybe it is time to for us ask to be on your list of companies using D? We have a number of prominent customers: www.ucora.com/clients

Thank you

On Saturday, 11 June 2022 at 04:30:17 UTC, Paul wrote:
>
> Regardless, I am thankful the group is at least considering it. It says a lot about how important D is to all of you. Let me know if there is anything I can do to help. If you feel it is appropriate and helpful, maybe it is time to for us ask to be on your list of companies using D? We have a number of prominent customers: www.ucora.com/clients
>
> Thank you

I’m not sure who is in charge of the website (Mike Parker?) but I am bumping thread for visibility — certainly Ucora should be added!

On Saturday, 11 June 2022 at 04:30:17 UTC, Paul wrote:
> maybe it is time to for us ask to be on your list of companies using D? We have a number of prominent customers: www.ucora.com/clients
>
> Thank you

You definitely should be on that list. No need to wait and hope to be included, though, just do it yourself! Press the “improve this page” link on the top right corner, and follow the instructions (you might need a Github account). You’ll be creating a pull request. The CI will automatically build a copy of the site so you can preview it. We have two PR managers aside from several others with merge rights, one of them will have a look at it and point you in the right direction if anything is lacking. If you get stuck don’t hesitate to ask here.

By the way, that link is on most pages of dlang.org, including the documentation, and it is the easiest way to bring about improvements. If anybody sees a way to make the documentation better, she should not hesitate to do so :-) It really is all up to us, the users.

— Bastiaan.

One possibility is to, for each page, set a link to a thread on the n.g. for that page. This would not require any changes to our setup.

Those threads would also be moderated so any off-topic posts are removed.