<br><br><div class="gmail_quote">On Sat, Jan 23, 2010 at 7:20 PM, Hans Dieter Pearcey <span dir="ltr"><<a href="mailto:hdp.perl.catalyst.users@weftsoar.net">hdp.perl.catalyst.users@weftsoar.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><br>
As far as I can tell, you missed the point of my message, which makes me wonder<br>
if I've missed the point of yours. Are you talking about a set of conventions<br>
you'd like to be able to build for your own use on top of HTTP::Body, or a set<br>
of conventions that you expect everyone will want and so should be built into<br>
HTTP::Body, or something else entirely?<br></blockquote><div><br></div><div>I thought you were saying that the request might not be a normal form posting, and I was saying only that HTTP::Body can support that, too.</div>
<div>I was not suggesting everyone should use one method over another.</div><div><br></div><div>HTTP::Body seems (to me) like the natural place to deserialize. Yet, the REST modules I cited use an action class to deserialize. Thus, I was wondering if there was a specific reasons for that approach that I had not understood. That's really all.</div>
<div><br></div><div><br></div><div><br></div><div><br></div></div><br>-- <br>Bill Moseley<br><a href="mailto:moseley@hank.org">moseley@hank.org</a><br>