On 7/5/07, Karen J. Cravens <[EMAIL PROTECTED]> wrote: > > On Jul 5, 8:19 pm, "Bob Ippolito" <[EMAIL PROTECTED]> wrote: > > with (the ones that you actually run into in the wild). It's easy to > > Given the increasing popularity of REST, seems pretty likely you'll > start running into a wider range of response codes "in the wild." > > It's kind of disturbing to learn it's that noncompliant; we haven't > settled on a library yet, but Mochikit was the front-runner for me. > Now I'm back to "I dunno, let's put all the names in a hat and pick > one," since Wirebird makes use of pretty much the full range of HTTP > responses.
As demonstrated it's effectively three lines of code to do whatever you want to do with HTTP status codes, and you only have to write it once. If that really makes such a difference, then I doubt MochiKit is the right choice for you. There are many cases where you actually have to write code, but MochiKit's behavior is well documented so at least you know what it's going to be doing. -bob --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MochiKit" group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit?hl=en -~----------~----~----~----~------~----~------~--~---
