<br><br><div class="gmail_quote">On Tue, Jan 26, 2010 at 6:33 AM, J. Shirley <span dir="ltr"><<a href="mailto:jshirley@gmail.com" target="_blank">jshirley@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div></div><div><br>
<br>
</div></div>I'm all for reusable code, but in no way should HTTP::Body start<br>
taking this behavior by default. I'm not really that sure how<br>
effective it is, anyway.<br></blockquote><div><br>No, I was not suggesting that would be the default (although I'm not
sure why not handling other serializations by default is a bad idea). Not sure what you mean by "effective".<br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
decode_json( $c->req->body ); Is just not that hard :)<br></blockquote><div><br>Of course it's not that hard. Of course, this isn't hard, either: [1]<br><br>map { s/%([0-9A-Fa-f]{2})/chr(hex($1))/eg; $_ } split /[&;=]/, $c->req->body;<br>
<br>I see those as similar operations. The request is serialized in both cases.<br>
<br>But, one should not have to worry about adding low-level details like that to application code when using an elegant web framework. ;)<br><br><br>No big deal. I was just curious why the HTTP::Body approach was not used in the existing REST/RPC modules, as that was already the place used by Catalyst to de-serialize the body. I thought maybe there was a reason I might not understood, which is why I asked.<br>
<br>[1] Or whatever the correct approach is, and apologies to Damian for the map.<br><br></div></div>-- <br>Bill Moseley<br><a href="mailto:moseley@hank.org" target="_blank">moseley@hank.org</a><br>