php-windows Digest 22 Jan 2004 10:34:45 -0000 Issue 2092
Topics (messages 22636 through 22640):
Running multiple versions of php on IIS
22636 by: Rainsford, David
22637 by: Frank M. Kromann
Re: Limitations with webservers. WAS: Show the Progress of a file
22638 by: Svensson, B.A.T. (HKG)
22639 by: Manuel Lemos
Re: Not about PHP, HTML question
22640 by: Dean Hayes
Administrivia:
To subscribe to the digest, e-mail:
[EMAIL PROTECTED]
To unsubscribe from the digest, e-mail:
[EMAIL PROTECTED]
To post to the list, e-mail:
[EMAIL PROTECTED]
----------------------------------------------------------------------
--- Begin Message ---
We have a new piece of software to roll out in the next week. The software
is built on PHP 4.3.4, but the webservers that we intend to use are also
running other websites which are only tested on PHP 4.0.4 or 4.1.2 or
something. Obviously ideally, we would like to upgrade the webservers to
4.3.4 but we can't afford to risk breaking the other sites. I figured we
would be able to install a second copy of PHP and use that for the latest
site. However, I want it using its own php.ini and IIS doesn't seem to like
me passing in the path to the php.ini using the -c option. Has anyone
managed to solve this problem, or do I have to share a common php.ini
between the different versions of php?
Thanks in advance,
David Rainsford
Software Engineer
Australian Council for Educational Research
19 Prospect Hill Road, Camberwell VIC 3124
t: 03 9277 5662
f: 03 9277 5500
e: [EMAIL PROTECTED]
w: www.acer.edu.au <www.acer.edu.au>
--- End Message ---
--- Begin Message ---
In order to ue multiple version of PHP on IIS I would think you need to use
the CGI version of php, and in that case you can have php.ini in the same
directory as the binaries.
You should also be able to have at least 1 version installed with the
ISAPI module.
- Frank
> We have a new piece of software to roll out in the next week. The
software
> is built on PHP 4.3.4, but the webservers that we intend to use are
also
> running other websites which are only tested on PHP 4.0.4 or 4.1.2 or
> something. Obviously ideally, we would like to upgrade the webservers
to
> 4.3.4 but we can't afford to risk breaking the other sites. I figured
we
> would be able to install a second copy of PHP and use that for the
latest
> site. However, I want it using its own php.ini and IIS doesn't seem to
like
> me passing in the path to the php.ini using the -c option. Has anyone
> managed to solve this problem, or do I have to share a common php.ini
> between the different versions of php?
>
> Thanks in advance,
>
> David Rainsford
> Software Engineer
>
> Australian Council for Educational Research
> 19 Prospect Hill Road, Camberwell VIC 3124
>
> t: 03 9277 5662
> f: 03 9277 5500
> e: [EMAIL PROTECTED]
> w: www.acer.edu.au <www.acer.edu.au>
>
>
--- End Message ---
--- Begin Message ---
I am a bit confused now.
We are talking about a progress bar at the client side, that
is to feed the enduser with progress information, or?
According to what Rich Stupek explainded to me in a private
e-mail the client upload the file in a syncrone simplex mode,
hence the client can't here any message passed back from
the web server. So whatever the webserver happen to do while
the client is uploading the file does not really matter(?).
In other words, a progress bar must be a client dependent thing?
-----Original Message-----
From: Manuel Lemos
To: [EMAIL PROTECTED]
Sent: 2004-01-21 21:47
Subject: [PHP-WIN] Re: Limitations with webservers. WAS: Show the Progress
of a file
Hello,
On 01/21/2004 12:01 PM, B.A.T. Svensson wrote:
>>You are confusing the types of progress. You can't track file upload
>>progress in PHP because PHP scripts only run after the file upload is
>>concluded. This is a limitation of PHP. Therefore that class alone is
>>useless.
>
>
> For me it seams to be a limitation with the webserver?
>
> Because even in principle php can't do this unless the
> web server permits/supports it - and I assume not many
> web servers does that? Or?
No, this can be done with Apache for instance in Perl but not in PHP
because PHP only starts executing the script after the upload has been
handled.
The Perl solution takes note of the size of the file that is being
transferred and another script can run in parallel to check the progress
and output a page that shows how it is going.
http://www.raditha.com/megaupload/
PHP can only do this with a patch. Somebody submitted a patch in the
php-internals mailing list but it seems nobody committed it.
--
Regards,
Manuel Lemos
Free ready to use OOP components written in PHP
http://www.phpclasses.org/
--
PHP Windows Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
--- End Message ---
--- Begin Message ---
Hello,
On 01/22/2004 04:59 AM, B.A.T. Svensson wrote:
I am a bit confused now.
We are talking about a progress bar at the client side, that
is to feed the enduser with progress information, or?
According to what Rich Stupek explainded to me in a private
e-mail the client upload the file in a syncrone simplex mode,
hence the client can't here any message passed back from
the web server. So whatever the webserver happen to do while
the client is uploading the file does not really matter(?).
In other words, a progress bar must be a client dependent thing?
No, client side is just one type of solution. It does not depend on the
server side language but usually you need Java applets or client side
add-ons that have plenty of inconvinients. While they generally work,
these necessary add-ons may not be available.
Another point is that client side view of progress is to show what was
sent, which is usually in advance of what was received. This distorts
progress and exhibit silly messages like 100% completed when the server
may take a while to receive everything.
The server side solutions measure what was received. You can't use the
same connection to send the form files and exhibit progress because the
browser is busy sending the files and will only show the resulting page
at the end.
Server side solutions work by using another HTTP connection opened in a
separate frame or window to show the progress reported by the connection
that is handling the data being received. See this solution for an example:
http://www.raditha.com/megaupload/
--
Regards,
Manuel Lemos
Free ready to use OOP components written in PHP
http://www.phpclasses.org/
MetaL - XML based meta-programming language
http://www.meta-language.net/
--- End Message ---
--- Begin Message ---
Just try and replace
<BODY bgcolor = "#7e8990" marginwidth="0" marginheight="0" topmargin="0"
leftmargin="35">
width
<BODY bgcolor ="#7e8990" marginwidth="0" marginheight="0" topmargin="0"
leftmargin="35" rightmargin="0" bottommargin="0"
note the extra rightmargin and bottommargin thi will ensure all sides of the
page have there margins set an not half of them it should work this time
Dean "The Insane Guy" Hayes
Mystical Web Designs
http://www.mystical-sector.com
<-- I design and i redesign but still i never designed true beauty like you
-->
From: "Disko_kex" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Subject: [PHP-WIN] Not about PHP, HTML question
Date: Wed, 21 Jan 2004 16:11:41 +0100
Hi,
I know this is a PHP mail list, but I have this enoying problem with
simple HTML. In my body a have:
<BODY bgcolor = "#7e8990" marginwidth="0" marginheight="0" topmargin="0"
leftmargin="35">
The problem I experience is that 100% is acully less then "visible"
100%, my design is based on a table (no frames) with height 100%. The
first time I load the page it's a about 10px in the bottom that's empty
and if I update the page it shows correctly (the empty space in the
bottom disappers). Its strange but its seems like 100% is less then 100%
the second time. Is there a way to do this in PHP or some another
langues so 100% is 100% of the visible browser size.
Thanks
//jocke
--
PHP Windows Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
_________________________________________________________________
Hot chart ringtones and polyphonics. Go to
http://ninemsn.com.au/mobilemania/default.asp
--- End Message ---
