webserver

The idea is that it leaves open a persistent connection with the webserver, which means A) less work creating and destroying connections B) each new connection isn't starting off as throttled.

Webserver is supposed to send all necessary user's data to Google server (like IP, UA, Cookies) and Google might ask Webserver to set google-specific Cookie.

A system installed on the webserver, where the webmaster offers ad-space which can be bought directly by the advertiser.

Orbited looks like an event-driven webserver, which is nice and all, but it doesn't magically give WebSocket functionality to legacy browsers.

If your webserver machines are so secure, why put them in the database at all?

PHP historically did not come with a disposable webserver, and writing one was hard.

I2P includes a webserver, to host the local configuration & status page.

In your approach they are stuck trusting the webserver and it's far easier to add fake page loads, this is somewhat less of an issue with PPC, but there are still issues.

> In your approach they are stuck trusting the webserver and it's far easier to add fake page loads, this is somewhat less of an issue with PPC, but there are still issues.

When the code base for everything on there server is going to be huge (aka they use Linux and any common webserver), there is pretty much a gaurantee that there will be a vuln, the only question is if someone will drop a zero day for this.

I'm thinking of a little Python script I wrote about a year ago, its sole purpose was to list unix permissions for each directory above the current one, something I occasionally need to do when tracking down reasons why a webserver might deny access to resources located within a directory.