Following up on our recent simulating discussion on adding an API to an
application, I wonder is someone can help me understand something:
Catalyst uses HTTP::Body to parse body content. It currently handles these
request content types:
our $TYPES = {
'application/octet-stream' =
On Sat, Jan 23, 2010 at 10:16 AM, Bill Moseley mose...@hank.org wrote:
Following up on our recent simulating discussion on adding an API to an
application, I wonder is someone can help me understand something:
Catalyst uses HTTP::Body to parse body content. It currently handles these
request
On Sat, Jan 23, 2010 at 1:40 PM, J. Shirley jshir...@gmail.com wrote:
If I assume that decoding is synonymous with de-serialization, it
makes more sense. At first thought, I just don't think they're that
similar, though. Maybe in implementations (comparing JSON to HTTP
POST parameters) it
Excerpts from Bill Moseley's message of Sat Jan 23 19:45:28 -0500 2010:
On Sat, Jan 23, 2010 at 1:40 PM, J. Shirley jshir...@gmail.com wrote:
If I assume that decoding is synonymous with de-serialization, it
makes more sense. At first thought, I just don't think they're that
similar,
On Sat, Jan 23, 2010 at 5:39 PM, Hans Dieter Pearcey
hdp.perl.catalyst.us...@weftsoar.net wrote:
Excerpts from Bill Moseley's message of Sat Jan 23 19:45:28 -0500 2010:
With a jpeg I assume the content type would be form-data (that included
an
upload in the form) where the file ends up in
Excerpts from Bill Moseley's message of Sat Jan 23 21:47:00 -0500 2010:
On Sat, Jan 23, 2010 at 5:39 PM, Hans Dieter Pearcey
hdp.perl.catalyst.us...@weftsoar.net wrote:
Excerpts from Bill Moseley's message of Sat Jan 23 19:45:28 -0500 2010:
With a jpeg I assume the content type would
