[Citadel Development] Re: START_CHAT_MODE is renamed to SEND_THEN_RECV
Me too, which is why it took me so long to get out of that headspace. The truth is, however, Citadel is extremely popular with the operators of small autonomous sites, not so much the "Exchange killer" I once thought it could become. That crap all moved to the cloud anyway. Even now as I am laying out the plans for the "home data center" I thought I would never need again ... I'm thinking multiple nodes and Kubernetes and PVE and/or Ceph and all sorts of other complex things when I could probably do better just running everything on one decent sized node.
[Citadel Development] Re: START_CHAT_MODE is renamed to SEND_THEN_RECV
Understood, was just a passing thought since i live in the 'big world' and first thought is always scale.. Many of our apps get 100k + connections all day long.
[Citadel Development] Re: START_CHAT_MODE is renamed to SEND_THEN_RECV
>That is a hard one. But keeping them separate might help with >scalability? That was true for WebCit-classic which contains a server-side user interface. And until a few years ago they could run on separate machines, so you could have multiple WebCit instances running with a load balancer. Today, the hardware is so powerful that this need no longer exists. We added a requirement for Citadel Server and WebCit to run on the same host because it makes TLS easy to deploy. Both programs can point to the same key and certificate files instead of having to get the components to trust each other over the network and then send everything back and forth. This is appreciated by innumerable site operators who "just want it to work" -- sites which actually exist in large numbers. Moving the web API would increase performance and possibly decrease complexity. However, it would be a major refactoring of the server code, which would be another year-long side quest. That's a bad thing when WebCit-NG is already years behind schedule. I've just begun work on the calendar. This is arguably the most logic-intensive part of the system and I want to keep it as DRY as possible. This is involving a lot of contemplation at a time when I really want to just get down to coding.
[Citadel Development] Re: START_CHAT_MODE is renamed to SEND_THEN_RECV
That is a hard one. But keeping them separate might help with scalability? Mon Jan 08 2024 12:42:10 EST from IGnatius T Foobar Subject: Re: START_CHAT_MODE is renamed to SEND_THEN_RECV I've been thinking lately that it might begin to make sense to put the web server (really, the web API) directly into Citadel Server. Since it's now a web API and no longer a user interface, it could be an improvement. *shrug*
[Citadel Development] Re: START_CHAT_MODE is renamed to SEND_THEN_RECV
I've been thinking lately that it might begin to make sense to put the web server (really, the web API) directly into Citadel Server. Since it's now a web API and no longer a user interface, it could be an improvement. *shrug*
