Embed PHP interpreter through PHP API, a replacement for CGI about phpdesktop

[GoogleCodeExporter]

Running "php.exe -f myscript.php" does resolve the firewall issue, as executing 
such command will also cause a firewall prompt. The ideal solution is to 
execute PHP script through PHP API, in PHP binaries there is a "dev/php5.lib" 
file, it looks like a static lib for the php5.dll, what we need is a php5.h 
header so we can call PHP API directly through php5.dll with no need to execute 
php5.exe. There seems to be no single "php5.h" file, it is probably required to 
download all sources codes of php5 from here:
http://windows.php.net/download/#php-5.4 > "Download source codes".

Original comment by [email protected] on 13 Jan 2013 at 2:46

[GoogleCodeExporter]

This will not work, unless we can implement a custom scheme,
without it we have no way to listen for coming requests.

Implementing a custom scheme is possible with Chrome, I'm not
sure about Internet Explorer, this feature will probably be
implemented only for Chrome.

Original comment by [email protected] on 13 Jan 2013 at 6:24

• Changed title: Chrome: execute scripts directly through PHP API call with no web-server listening

[GoogleCodeExporter]

When executing php script directly how do we set the document root?

Original comment by [email protected] on 14 Jan 2013 at 8:51

[GoogleCodeExporter]

The source of the "php.exe" can be found in sapi/cli/php_cli.c, function that 
interests us is "php_execute_script":

https://github.com/php/php-src/blob/master/sapi/cli/php_cli.c#L988

Original comment by [email protected] on 15 Jan 2013 at 5:08

[GoogleCodeExporter]

Calling PHP API directly would require implementing multi-threading
if we want to support handling multiple requests at the same time.
PHP built-in webserver is also single threaded, it cannot handle more
than one request at the same time, see Issue 14.

Original comment by [email protected] on 15 Jan 2013 at 5:27

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

We will still need a web-server, otherwise submitting forms and uploading files
won't work. The solution would be to implement a virtual file system (VFS) in 
the
mongoose web-server. Or maybe PHP API already has a VFS mechanism?

Original comment by [email protected] on 2 Feb 2013 at 3:38

• Changed title: Chrome: execute scripts using PHP API calls

[GoogleCodeExporter]

VFS in mongoose web-server is not enough, as php scripts include other php
scripts, so it must be some kind of VFS in PHP API.

Original comment by [email protected] on 2 Feb 2013 at 3:53

• Changed title: Execute PHP scripts through PHP API

[GoogleCodeExporter]

We need VFS in both Mongoose & PHP API.

Original comment by [email protected] on 2 Feb 2013 at 3:56

[GoogleCodeExporter]

To use an in-memory file system in Mongoose web-server you have to
implement "open_file" callback, example here:

https://github.com/valenok/mongoose/blob/ee55d38b5592cbb55b78c74c2c36fc768fc22a0
7/test/unit_test.c#L192

Original comment by [email protected] on 2 Feb 2013 at 5:29

[GoogleCodeExporter]

See this topic for an in-memory filesystem with Mongoose:
https://groups.google.com/d/topic/mongoose-users/JhNQFKC_0wI/discussion

Original comment by [email protected] on 2 Feb 2013 at 5:57

[GoogleCodeExporter]

See Kroll's PHP module:
https://github.com/appcelerator/kroll/tree/master/modules/php

Original comment by [email protected] on 4 Feb 2013 at 4:22

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

When PHP is run in other way than through CGI, memory leaks might be a problem.

Original comment by [email protected] on 13 Feb 2013 at 6:11

[GoogleCodeExporter]

This is not a good idea to execute PHP using the PHP API, as PHP was never 
intended to run long hours and this could result in memory leaks.

Original comment by [email protected] on 19 Jan 2014 at 7:24

• Changed state: WontFix