And thank you for the chance to not look like a dummy for a change. :)
On Jan 9, 2008, at 1:32 PM, Daniel McBrearty wrote:
Thanks Ashley, that did indeed fix the JSON problem!
(wish I'd remembered to write a test *before* I fixed it like this
though ;-)
cheers
Daniel
On Jan 7, 2008 9:28
Thanks Ashley, that did indeed fix the JSON problem!
(wish I'd remembered to write a test *before* I fixed it like this though ;-)
cheers
Daniel
On Jan 7, 2008 9:28 PM, Ashley Pond V <[EMAIL PROTECTED]> wrote:
> This may or may not be germane: try installing JSON::XS and updating
> your JSON an
This may or may not be germane: try installing JSON::XS and updating
your JSON and JSON::Any. JSON::XS is one of, if not the, fastest
serializers in all data classes and its utf8 handling is better. JSON
now, IIRC, calls it if it's present instead of its older Perl version.
-Ashley
On Jan
well, the moral is probably "never work on your code when recovering from flu".
It was pretty much a self-induced problem. I have a system where the
user submits a value, and the value is copied back to them. If there
is a network problem with corruption of the data, they will see it, as
the retur
On 06/01/2008, Daniel McBrearty <[EMAIL PROTECTED]> wrote:
> >
> > In any case the raw HTTP request that leads to all this would be
> > interesting.
> >
>
> I can tell you that the data in the raw request is just the 9 bytes of
> UTF8, exactly as shown by Dumper. I looked at it with wireshark to be
On 06/01/2008, Daniel McBrearty <[EMAIL PROTECTED]> wrote:
> so do you mean that Dumper should be seeing and outputting this as a
> char sequence? (what it actually shows is a mix of chars and hex
> bytes, in fact ...)
No, dont get confused. Everything that dumper output is chars, it just
happens
>
> In any case the raw HTTP request that leads to all this would be
> interesting.
>
I can tell you that the data in the raw request is just the 9 bytes of
UTF8, exactly as shown by Dumper. I looked at it with wireshark to be
sure.
To give some background, this is getting pulled out of a form by
so do you mean that Dumper should be seeing and outputting this as a
char sequence? (what it actually shows is a mix of chars and hex
bytes, in fact ...)
On Jan 6, 2008 2:08 PM, Aristotle Pagaltzis <[EMAIL PROTECTED]> wrote:
> * Daniel McBrearty <[EMAIL PROTECTED]> [2008-01-06 13:30]:
> > On Jan 6
because it is utf8? shouldn't it be?
On Jan 6, 2008 1:29 AM, Aristotle Pagaltzis <[EMAIL PROTECTED]> wrote:
> * Daniel McBrearty <[EMAIL PROTECTED]> [2008-01-06 00:00]:
> > [debug] abçöeü
> > [debug] $VAR1 = "ab\x{c3}\x{a7}\x{c3}\x{b6}e\x{c3}\x{bc}";
> > [debug] it's UTF8!
>
> Err, why doesn't Dum
