I understand the basis about what your telling me, but I’m still convinced that way it’s a good way to scale.

>I also think that many see “C daemon with embeded PHP” and

>wonder “So, what’s mod_php inside Apache then?”.

>You don’t explain that.

My idea it’s separate the website, in services, i.e In you Apache (mod_php) you have basic routine to show the page, then you create an application and put on the Appserver (you write a service), called Register_User, from you Apache you can request the execution of that function, and it returns something, in this case true if success otherwise false.

If the Register_User function does a lot of things, perform a select over a sql table, find duplicated e-mail, validate all those data. The whole overhead it’s perform in another server, and you mod_php waits the answer. Since the Apache will be idle waiting, it will be able to handle other request.

My idea it’s not replace Apache, nor create a new kinda Webserver. My goal it’s provide a way to distribute work over machines, in order to have small process on the front, and hard process on over machines.

Additional my idea was added “procedures” and “functions”, “functions” returns something, “procedures” does not (a.k.a Queue something for a late execution).

It is clear enough?

P.S: Regard the comment edit, it is WP, not my fault this time ;).
P.S: Once again, thanks for you comment.

The last thing should read “I’m trying to stay neutral.”.

And something to add about caching: HTTP caching is well known and well understood; just in case you’re proposing a new cache technique which hasn’t seen the light yet you’ve to explain why it’s better to go from scratch.

If it’s about performance, where are the performance savings.

Ok, I’ll stop. I’m not the one to convince anyway. I’m just trying to write down what I think people visualize about your idea. I can be wrong, don’t forget that

Some things ahead: if you explain “Some concepts” and provide a graph without labeling all of the concepts, it’s confusing. Apply the Client/Worker terms into the graph.

I think people find it hard to grok the C-Daemon thing. You’ve just provided architectural concepts and the daemon “looks” heavy weight. Heavy things are not everyone friends. If it can be light-weight, provide some insights why and how.

I also think that many see “C daemon with embeded PHP” and wonder “So, what’s mod_php inside Apache then?”. You don’t explain that.

Why can’t a Worker be just a well-proven-tested-has-been-around-for-decades-apache-instance instead some proprietary-looking-from-scratch-written-and-thus-probably-bug-ridden daemon?

What interchange formats are you proposing?

Since the dawn of PHP4 in May 2000 there have been zillions approaches of App-Servers, Distributed Environments, Self-Running-Daemons and whatnot. None of them *really* succeeded.

Too complex for developers, too many bugs, looked fine on paper but didn’t do well (in whatever aspect) when done, too hard to use, no useful documentation, support, etc.

So. I’m trying to stay object. For me this concept needs to be fleshed out better, thinking ahead.

Good luck!