Request: howto use a CLI php script at webserver (webconsole)?

i have some scripts made for use as a CLI scripts from the console.

but i like use this scipts from a webbrower.

i dont like to patch the scripts too much.

the script uses the stream wrapper:

php://stdin
php://stdout
php://stderr


possible solutions:

1) a wrapper to wrap over the php://sdt* streams
2) change the php://sdt* streams to a new wrapper (like webphp://sdt )



is there already a working solution?
maybe with use of ajax?

On Aug 13, 12:20 am, Michael N <nietz...@gmail.com> wrote:
> i have some scripts made for use as a CLI scripts from the console.
>
> but i like use this scipts from a webbrower.
>
> i dont like to patch the scripts too much.
>
> the script uses the stream wrapper:
>
> php://stdin
> php://stdout
> php://stderr
>
> possible solutions:
>
> 1) a wrapper to wrap over the php://sdt* streams
> 2) change the php://sdt* streams to a new wrapper (like webphp://sdt )
>
> is there already a working solution?
> maybe with use of ajax?

I think, you might be knowing... anyway, fopen('php://stdin', 'r');
on command line is getting input from command line and on webserver
environment, it's reading from POST.

--
<?php echo 'Just another PHP saint'; ?>
Email: rrjanbiah-at-Y!com Blog: http://rajeshanbiah.blogspot.com/

Michael N wrote:
> i have some scripts made for use as a CLI scripts from the console.
>
> but i like use this scipts from a webbrower.
>
> i dont like to patch the scripts too much.
>
> the script uses the stream wrapper:
>
> php://stdin
> php://stdout
> php://stderr
>
>
> possible solutions:
>
> 1) a wrapper to wrap over the php://sdt* streams
> 2) change the php://sdt* streams to a new wrapper (like webphp://sdt )
>
>
>
> is there already a working solution?
> maybe with use of ajax?
>

Actually, something like this I would put the common stuff in classes or
functions. Then include it in both the command line and web page files.

Much more portable, and cleaner.

--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================

>
> Actually, something like this I would put the common stuff in classes or
> functions. Then include it in both the command line and web page files.
>
> Much more portable, and cleaner.
>

thats right. but i like to make a webconsole for existing CLI
scripts.
thats why i dont like to change too much the existing scripts.

if i change the existing scripts too much it is a big trouble if the
scripts are updated.

my idea is to make a webconsole for the CakePHP bake script.
the bake script make the output to the user via php://stdout and wait
then for input via php://stdin.