I got it.
In fact, if the buffer is bad, it is not erased, and Buffered() returns it
(and not the following).
That was my misunderstanding.
Thank you all !
On Thursday, 27 December 2018 00:31:12 UTC+1, Kevin Conway wrote:
>
> > I believe https://golang.org/pkg/encoding/json/#Decoder.Buffered
> I believe https://golang.org/pkg/encoding/json/#Decoder.Buffered was
added for this purpose.
I just caught on that this method is exactly what you showed in the
original message. I guess my input can be reduced to "I think that's your
only option when using the decoder".
I do think you've
> For example, the error returned may show : "*invalid character 'G'
looking for beginning of value*". But you can't see the original message.
I believe https://golang.org/pkg/encoding/json/#Decoder.Buffered was added
for this purpose. For example, https://play.golang.org/p/yAn2fypIELc
> 1- I'm
You haven't shown the code, so I don't know.
json.Decoder can decode json streams - one object at a time (separated by
whitespace).
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from
Sorry I don't get it ?
My decoder is already built with it.
Thank you,
Thomas
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
Try json.NewDecoder.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit
Hello,
I need help to improve the reliability of a proxy and numerous servers in
Golang, currently in use by a certain number of users.
I receive json stream by TCP and websocket.
The only way to do it properly is to used json decode.
(notably because websocket payload system can split in
