"John Coggeshall" <[EMAIL PROTECTED]> wrote... :

> 
> My bad then :) I was under the impression that we had moved passed this
> and no one had a real issue with it.
> 
> I'll hold off on it then. 


Only because I18N thingie has smoothen it off doesn't mean we should get
error redirects already in :)

But, seriousely speaking, since there is no agreement on anything yet, let's
wait.

--
Maxim Maletsky
[EMAIL PROTECTED]





> 
> John
> 
> >-----Original Message-----
> >From: Sterling Hughes [mailto:[EMAIL PROTECTED]] 
> >Sent: Tuesday, November 26, 2002 3:18 PM
> >To: John Coggeshall
> >Cc: 'Ivan Ristic'; 'James Aylett'; 'PHP Developers Mailing List'
> >Subject: Re: [PHP-DEV] Redirect on Error (not localisation)
> >
> >
> >> 
> >> Unless told otherwise, I'm already planning on making a few changes 
> >> and committing.
> >>
> >
> >john,
> >
> >I've told you otherwise, so has derick and about half the 
> >developers on this list (not talking about the localization 
> >portion of the thread here).
> >
> >Quick answer: don't.  If you wanna come with some patches, 
> >post them on your website, i and other people will be happy to 
> >look @ them and discuss them, 
> >but *do not* commit them without a reasonable concensus.
> >
> >-Sterling
> >
> >> John
> >> 
> >> 
> >> >-----Original Message-----
> >> >From: Ivan Ristic [mailto:[EMAIL PROTECTED]]
> >> >Sent: Tuesday, November 26, 2002 2:50 PM
> >> >To: [EMAIL PROTECTED]
> >> >Cc: 'James Aylett'; 'PHP Developers Mailing List'
> >> >Subject: [PHP-DEV] Redirect on Error (not localisation)
> >> >
> >> >
> >> >
> >> > > Anyway... So what of my actual patch we were discussing at some 
> >> > > point? I never got a real answer as to if it would be 
> >suitable to 
> >> > > commit.
> >> >
> >> >    I have changed the subject of the message in an effort to
> >> >    separate the discussion on the "Redirect on Fatal Error" feature
> >> >    (the subject of this email) from the localisation discussion.
> >> >
> >> >    ...
> >> >
> >> >    As a reminder, we are discussing a patch that will redirect
> >> >    the user to another page when a fatal or a parse error occurs
> >> >    (parse errors can be caught with lint, fatal can't). The
> >> >    redirection will allow developers to:
> >> >
> >> >    * Show a decent page to the user (instead of letting them
> >> >      see a blank or incomplete page)
> >> >
> >> >    * Send a message to themselves that something
> >> >      strange has happened (allowing them to react quickly, instead
> >> >      of having to install log watch software for notification
> >> >      purposes (and many people cannot do that as they do not
> >> >      have control over the servers))
> >> >
> >> >    As far as I am aware, there is not a single reason not to
> >> >    have this feature. Some people seem not to like it, but that
> >> >    is fine; with no performance or stability risks, if you don't
> >> >    want to use the feature - you won't be affected.
> >> >
> >> >    On the other hand, I will be extremely happy to have it under
> >> >    my belt as yet another tool I can use to make my software
> >> >    run better.
> >> >
> >> >    Please don't tell me that I wouldn't need this feature if
> >> >    I programmed perfectly. Errors happen all the time, no matter
> >> >    what you do trying to prevent them.
> >> >
> >> >
> >> >Bye,
> >> >Ivan
> >> >
> >> >
> >> >
> >> >
> >> >--
> >> >PHP Development Mailing List <http://www.php.net/>
> >> >To unsubscribe, visit: http://www.php.net/unsub.php
> >> >
> >> >
> >> 
> >> 
> >> --
> >> PHP Development Mailing List <http://www.php.net/>
> >> To unsubscribe, visit: http://www.php.net/unsub.php
> >> 
> >
> 
> 
> -- 
> PHP Development Mailing List <http://www.php.net/>
> To unsubscribe, visit: http://www.php.net/unsub.php
> 


-- 
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to