[Rt-devel] REST: differentiating errors by RT status.

[Jesse Vincent]

On Jul 28, 2006, at 9:31 AM, Dmitri Tikhonov wrote:

> Dear fellow RTers,
>
> I think that server-side REST code should indicate success or  
> failure of
> operation by utilizing "RT code".  For example, fetching a ticket that
> does not exist returns the following:
>
>    RT/3.4.5 200 Ok
>
>    # Ticket 4 does not exist.
>
> Maybe it should return
>
>    RT/3.4.5 404 Not Found
>
>    # Ticket 4 does not exist.
>
> So that the client can just *know* that something's amiss by  
> looking at the
> RT code (easy) instead of parsing output for things like m/does not  
> exist/
> (error-prone).
>
> Thoughts?

I like it, so long as it doesn't break existing clients ;)

Best,
Jesse



>   - Dmitri.
>
>
> _______________________________________________
> List info: http://lists.bestpractical.com/cgi-bin/mailman/listinfo/ 
> rt-devel
>
> Best Practical is hiring! Come hack Perl for us: http:// 
> bestpractical.com/about/jobs.html
>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
Url : http://lists.bestpractical.com/pipermail/rt-devel/attachments/20060731/97078d61/PGP.pgp