Using Drupal as a base and other factors, there's no way that this module will be all that efficient, but it would still be a good performance increase to add a proxy.php file that someone can copy to their Drupal root. This file would only bootstrap the necessary Drupal parts, and then manually do the rest.

Comments

dman’s picture

dman CreditAttribution: dman commented
Status: Active » Postponed

Very good idea.
Will be incompatible with support for Drupal permissions however. That's an OK trade-off, though will need a different approach to security.

Current code already keeps the bulk of the processing in processor.inc, so good.
Current code relies on the ctools architecture to invoke plugins, so that can't work without a bootstrap?
... Hm. Looking it over, there is now a good amount of Drupal API stuff that would have to be pulled out to make it work stand-alone. Especially any variable_get, which includes the URL whitelist.
Or perhaps we can drupal_bootstrap() just to a point before the database loads.
...
..

Hm. Would be a lot of work for ?? gain.
Deferring this until someone wants to sponsor it or needs it for a good reason.
If performance is a thing for you, use Apache mod_proxy. Trying to go half-assed about it here would be a security hole liable to be exploited.