Why can’t the PHP engine handle HTTP communication?
The PHP engine interprets the PHP code and is perfectly capable of working with sockets, forming HTTP packets, etc. Why then do we need a separate Apache server, when the http serving duties could be embedded into the php application along with the page creation code?
What is the difference between a server and a mainframe? [closed]
Closed 11 years ago.
Which .NET technology would work as an improvement for this client/server application?
I am helping a friend with his rewrite of his .NET application, currently using WinForms + sockets, which is a client/server program that currently has on average ~120 concurrent users (sending messages, using the chat). The client will grow and eventually must be able to handle a several thousand concurrent users.
Should I re-download my server data after each change?
I have a simple DB editor that sits on the client. When I make changes via the editor, should I re-get all my data, as some of it is changed, or can I just do a check to make sure the procedure ran without error and assume my data is the same as the server?
Why not use a RTOS with microkernel architecture for highly concurrent web servers?
Why not use a RTOS with microkernel architecture for web servers? The scheduler is deterministic and all requests will be handled quickly leading to faster response time? It’s easy to extend an OS based on microkernel architecture, since everything is like a client-server communication via message passing. Also, the server will be very light weight and requires less resources. Say that you are developing the web service using C++. I am thinking about QNX for the OS. Is it a bad idea, or it does not matter?
What is the best/most standard way to measure server load?
I’m a bit green to web applications although I am in the final phases of developing one for a client. I’m using Django with Gunicorn/Nginx on an AWS m1.medium. The database (MongoDB) is on a separate instance. The client is paranoid about scaling and so I threw together a crude monitoring server which has the ability to spin up new AWS instances, install the app code and load balance (I know, I know, I could have used ELB. I said I was green, and it was fun writing it anyway).
What is the best/most standard way to measure server load?
I’m a bit green to web applications although I am in the final phases of developing one for a client. I’m using Django with Gunicorn/Nginx on an AWS m1.medium. The database (MongoDB) is on a separate instance. The client is paranoid about scaling and so I threw together a crude monitoring server which has the ability to spin up new AWS instances, install the app code and load balance (I know, I know, I could have used ELB. I said I was green, and it was fun writing it anyway).
What is the best/most standard way to measure server load?
I’m a bit green to web applications although I am in the final phases of developing one for a client. I’m using Django with Gunicorn/Nginx on an AWS m1.medium. The database (MongoDB) is on a separate instance. The client is paranoid about scaling and so I threw together a crude monitoring server which has the ability to spin up new AWS instances, install the app code and load balance (I know, I know, I could have used ELB. I said I was green, and it was fun writing it anyway).
What is the best/most standard way to measure server load?
I’m a bit green to web applications although I am in the final phases of developing one for a client. I’m using Django with Gunicorn/Nginx on an AWS m1.medium. The database (MongoDB) is on a separate instance. The client is paranoid about scaling and so I threw together a crude monitoring server which has the ability to spin up new AWS instances, install the app code and load balance (I know, I know, I could have used ELB. I said I was green, and it was fun writing it anyway).
How can a developer working alone respond to a spike in server demands?
Imagine this scenario: