RE: Re[2]: [PHP] PHP vs. ColdFusion

2005-07-01 Thread Andrew Scott
Actually that's not true, reply to: is not a hack and is very much a standard to include in the headers, its part of the rfc standard, after having written a mail server as a project its not hard to create a mailinglist option that sets this info up properly. If you setup your mail client with th

RE: [PHP] PHP vs. ColdFusion

2005-07-01 Thread Andrew Scott
meant to be used on online servers. -Original Message- From: Stut [mailto:[EMAIL PROTECTED] Sent: Saturday, 2 July 2005 12:50 AM To: Andrew Scott Cc: php-general@lists.php.net Subject: Re: [PHP] PHP vs. ColdFusion Andrew Scott wrote: > Hey it's not my fault that this s

RE: [PHP] PHP vs. ColdFusion

2005-07-01 Thread Andrew Scott
Well I am on about 20-30 as well, and when I press reply it goes to a mailinglist address for broadcasting not the posters email address. -Original Message- From: George Pitcher [mailto:[EMAIL PROTECTED] Sent: Saturday, 2 July 2005 12:26 AM To: Andrew Scott; 'John Nichel'; p

RE: [PHP] PHP vs. ColdFusion

2005-07-01 Thread Andrew Scott
aturday, 2 July 2005 12:15 AM To: php-general@lists.php.net Subject: Re: [PHP] PHP vs. ColdFusion Andrew Scott wrote: > Hey it's not my fault that this stupid list needs a reply all! Learn how to use your mail client instead of expecting someone to bastardize the email headers. Andrew, me

RE: [PHP] PHP vs. ColdFusion

2005-07-01 Thread Andrew Scott
Hey it's not my fault that this stupid list needs a reply all! I am going to guess Stut, that you don't know even know what the difference between a singleton instantiated object is to a standard instantiated object? You know for a php developer your really don't know your own product to well, a

RE: [PHP] PHP vs. ColdFusion

2005-06-30 Thread Andrew Scott
tremely secured. -Original Message- From: Brad Pauly [mailto:[EMAIL PROTECTED] Sent: Thursday, 30 June 2005 10:54 PM To: php-general@lists.php.net Subject: Re: [PHP] PHP vs. ColdFusion On 6/30/05, Andrew Scott <[EMAIL PROTECTED]> wrote: > Cons for PHP: > - > Coldfu

RE: Re[2]: [PHP] PHP vs. ColdFusion

2005-06-30 Thread Andrew Scott
Richard, And your point of before you pay your programmer is what one of my other points was. CF is very rapid development, and you might say the same about PHP. The point is that these are all the things you need to take into consideration, the cost that it would take to develop and maintain i

RE: [PHP] PHP vs. ColdFusion

2005-06-30 Thread Andrew Scott
ice that I am trying to put forward, not whether this language is better than that, but more of an open mind to what each can and can't do. Regards Andrew Scott Analyst Programmer CMS Transport Systems Level 2/33 Bank Street South Melbourne, Victoria, 3205 Phone: 03 9699 7988 - Fa

RE: [PHP] PHP vs. ColdFusion

2005-06-29 Thread Andrew Scott
Rick, Yes a framework can be built in PHP, C# or any language but how would you like to design something like this. The above is tags that I am referring to very similar to java tag libraries, these tags read data from a database, validate and display the data like windows .net form

RE: [PHP] PHP vs. ColdFusion

2005-06-29 Thread Andrew Scott
l be looking at the overall cost, development cost and maintenance cost and this can be very expensive, if you don't do your homework first, and with blue dragon you don't need to spend a cent to develop in coldfusion. Regards Andrew Scott Analyst Programmer CMS Transport Systems Lev

Re: [PHP] PHP 4.3.2 released

2003-05-31 Thread Andrew Scott
Hi, This _still_ doesn't seem to work with Linux/Apache2. I have no problems with Apache 1.3.27. Have been running Apache/php for years, but I have been unable to get php to work with apache2 except as a cgi. I have now tried both --with-apxs2 and --with-apxs2filter. Neither appear to work. Us

Re: [PHP] Apache 2.0

2002-04-11 Thread Andrew Scott
On 11 Apr 2002 at 14:37, Marcin Pasieka wrote: > How to install PHP on Apache 2.0 server? > As far as I can see, at the moment, the only way is to use cgi. It looks like that API stuff has to be rewritten/updated a little. However, since Apache 2 is now released, the API shouldn't be changing