Posted by Jerry Stuckle on 03/02/06 00:57

Jan wrote:
> We expect about 570 new visitors every minute on our web page, 17 of
> these will press the submit button to invoke the PHP.
>
> Would you expect the performance hit to noticeable at this volume, this
> we should consider a cgi-bin perl instead of PHP. Perl is never invoked
> unless submit is pressed.
>
> We would also like to store the referrer in a cookie when someone
> enters the page, this could be done with PHP. Maybe javascript is
> quicker?
>

570 visitors a minute isn't a whole lot for a fast server. You won't
see much impact by loading PHP. Of course, if you have a slow server,
you'll see the impact - but there are many other things which will cause
a bigger impact.

BTW - Perl and PHP are both server-side languages and do much the same
thing. You can design the PHP pages just like the Perl ones - and each
parser will be invoked for its respective web page.

As for the referrer - you would have to do that on the incoming page,
which means PHP or Perl on the server side, or Javascript on the client
side.

However, this is VERY unreliable. The user may have disabled
javascript, for instance. And even if they did, or you use PHP or Perl,
HTTP_REFERER is not dependable. The browser may or may not send it, and
even if they send it, a firewall may block it.


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

[Back to original message]