You always can have 2 stages of parsing

# klaxon

[gildor]

You always can have 2 stages of parsing

[gildor]

@dave08 I mean parse once, just to detect which of them is not null, then parse again as error/result

[dave08]

Nope, I need two stages because I don't know to what type I'll be parsing the result at this stage...

[gildor]

But why? you should know result type, because you know request type

[cedric]

It's pretty common to have two stages of parsing, I remember the Facebook API having a lot of that

[gildor]

Cedric, but on your experience, what would be more efficient:
1. parse result to string/any
2. parse it to something like Gson’s JsonObject, so it can be faster to map this later to a class?

[cedric]

My experience is not a reliable benchmark 🙂

[cedric]

Measure.

[cedric]

But overall, I wouldn't worry too much, these extra JSON payloads are usually not that big

[cedric]

but you can probably get fancy with the streaming API if you want to avoid overhead

[cedric]

read each field as it comes, wait for the type one, then you know how to parse the string when it comes in

[gildor]

Yeah, sure. Just curious. Because it’s so common case

[dave08]

But it might still be practical to have a rawJsonString property in JsonValue? Or is there already? That way a field converter could be made for this...

[dave08]

My payloads are requests that could potentially retrieve an array of lots of objects... it might be nice to avoid the extra step.

The streaming doesn't help, since my JsonRpc client is seperate from the one actually parsing the payloads...

[dave08]

So I won't know the type yet...

[dave08]

So so far it's either using JsonValue type for result...?