From: Stephen Leake <stephen_leake@stephe-leake.org>
Subject: Re: gnatcol json vs network read
Date: Fri, 14 Dec 2018 11:00:35 -0800 (PST)
Date: 2018-12-14T11:00:35-08:00 [thread overview]
Message-ID: <75c6e8f5-c564-4ded-8314-7f12612fe991@googlegroups.com> (raw)
In-Reply-To: <a57563c9-8f79-47a5-8613-ebd975899fa8@googlegroups.com>
On Friday, December 14, 2018 at 9:50:10 AM UTC-8, Stephen Leake wrote:
>
> So I guess I'll write a {} counter, and wait for more data from the network if the first object is not complete.
Arg. The problem turned out to be the client (an Android app) is sending ' as UTF-8 16#e28099# instead of ASCII ', throwing off the byte count. sigh.
There should still be an incomplete object problem, but apparently I haven't actually seen it yet.
-- Stephe
next prev parent reply other threads:[~2018-12-14 19:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-14 17:50 gnatcol json vs network read Stephen Leake
2018-12-14 18:53 ` Olivier Henley
2018-12-14 19:00 ` Stephen Leake [this message]
2018-12-14 21:58 ` Per Sandberg
2018-12-15 9:41 ` Stephen Leake
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox