I've noticed that under certain conditions the HTTP request throws exception during parsing and I've found that it was successfully parsed, but then the result was thrown away in CompositeSerializer. I've put in a fix - pass on the result or return null.
I've also added support for QueryString. The additional overhead is minimal (assigns null in the constructor) and the actual collection is generated on demand.
Hello,
I've noticed that under certain conditions the HTTP request throws exception during parsing and I've found that it was successfully parsed, but then the result was thrown away in CompositeSerializer. I've put in a fix - pass on the result or return null.
I've also added support for QueryString. The additional overhead is minimal (assigns null in the constructor) and the actual collection is generated on demand.