NYCPHP Meetup

[Daniel Convissor]

Howdy:

On Fri, Mar 10, 2006 at 12:19:32PM -0500, David Mintz wrote:
> 
> Is there a convention/best practice for throwing an
> error to signal the client something is wrong -- e.g., do you send an HTTP
> error code in a header or some such? Or just echo something like
> <error>error message here</error>?

The application I'm working on along these lines returns an error 
code/message in the body, not the header.  Provides more fexibility in 
explaining the issue to the front end/users.

--Dan

-- 
 T H E   A N A L Y S I S   A N D   S O L U T I O N S   C O M P A N Y
            data intensive web and database programming
                http://www.AnalysisAndSolutions.com/
 4015 7th Ave #4, Brooklyn NY 11232  v: 718-854-0335 f: 718-854-0409