RE: RE: [Formaldehyde] The Most Basic Ajax - PHP ErrorDebugger

--_10cfd061-645f-4048-8fe4-5b12e9691ee9_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


Right=2C errors should never be exposed=2C and error_reporting should be 0 =
in production but log function and the fact you can move Formaldehyde with =
the application means it does not require extra effort.

In few words=2C if in production Formaldehyde constant is false=2C and it m=
ust be false=2C nothing will be exposed.

You do not need to change your code if you configure properly the defined c=
onstant while you can use what logs have to offers plus you'll have 1:1 pro=
duction/development application

Finally=2C locally=2C and at least for me=2C I find extremely useful the ru=
ntime debug=2C rather than keep logs under control=2C since specially Ajax =
interactions needs to be performed runtime via emulators (Selenium) or not =
(We testing) and other applications I know do not offer this simplicity tha=
t you call "useless" but which is the reason I have created Formaldehyde.

That simplicity is not offered so far by your suggested one as well=2C and =
please tell me how quick could be an instant PHP error "on screen" during t=
ests or debug rather than a log analysis but in any case=2C thanks for the=
feedback.

This is the only serious analysis so far=2C and I am looking forward for ot=
hers=2C if any.

Best Regards

> The thing is=2C in a properly configured development environment=2C it's
> local=2C so I can immediately read the logs=2C or just fire the script up
> with xdebug=2C or the errors will get caught in the editor. And I would
> NEVER imagine publicly exposing error messages in a production
> environment=2C so I'm just really confused as to what this offers=2C othe=
r
> than some seemingly small benefit in readability=2C specifically in
> firebug (and some other cruft that you really ought to remove=2C like
> the X-Formaldehyde header). And furthermore=2C this requires code
> changes from development -> production=2C which is a problem I've always
> had with FirePHP=2C too=2C as that information does not belong in a
> production environment. As far as support for shared hosting is
> concerned=2C I've stated on this list several times that my firm opinion
> is shared hosting is shooting yourself in the foot (especially as a
> good VPS isn't that much more expensive=2C I'm paying $20/mo for mine).
>=20
> I think you best summed up why so many on this list think Formaldehyde
> isn't a very useful product yourself: the errors are shown on the
> client side. In theory=2C a good development environment already
> exposes this information to the developer and things should fail a lot
> more gracefully than error output for the user. You said that this
> project is something that doesn't already exist=2C perhaps you should
> consider that it doesn't exist because a sane development cycle
> precludes Formaldehyde's usefulness?
>=20
> --=20
> PHP General Mailing List (http://www.php.net/)
> To unsubscribe=2C visit: http://www.php.net/unsub.php
>=20

____________________________________________________________ _____
Show them the way! Add maps and directions to your party invites.=20
http://www.microsoft.com/windows/windowslive/products/events .aspx=

--_10cfd061-645f-4048-8fe4-5b12e9691ee9_--