QUOTED:[EMAIL PROTECTED], the opposite of the PHP approach :^)
Hey! I resent that. In my many years of back-end Php programming (or,
if you want to split hairs, scripting) Php hasn't even crashed once.
And if it did crach, it wouldn't bring down the server. I have
mis-configured it multiple
On 10/31/05, Nick Kew [EMAIL PROTECTED] wrote:
On Monday 31 October 2005 13:58, Olaf van der Spek wrote:
Hi,
What is the (best) way to connect a C++ server with Apache?
What's the language got to do with it?
Not much, but if it was PHP, mod_php would be an alternative.
Use whatever
On Monday 31 October 2005 15:02, Olaf van der Spek wrote:
Use whatever protocol your
backend supports.
I don't have an existing backend.
In fact, I've got nothing at all yet for this project.
So you could just write it as a module?
AJP looks usable, but I'm not sure if it's the right
On 10/31/05, Nick Kew [EMAIL PROTECTED] wrote:
On Monday 31 October 2005 15:02, Olaf van der Spek wrote:
Use whatever protocol your
backend supports.
I don't have an existing backend.
In fact, I've got nothing at all yet for this project.
So you could just write it as a module?
On Monday 31 October 2005 15:25, Olaf van der Spek wrote:
I don't have an existing backend.
In fact, I've got nothing at all yet for this project.
So you could just write it as a module?
No, because I'd like it to be (more) independent of the web server.
Apache could be either
On 10/31/05, Nick Kew [EMAIL PROTECTED] wrote:
No, because I'd like it to be (more) independent of the web server.
Apache could be either multi-threaded or multi-processed, but my app
would be single-threaded (epoll).
That's a lot of constraints to be putting on yourself if they're
not
