incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jesse <>
Subject Re: [WP7] Passing more complex objects over the bridge
Date Tue, 19 Jun 2012 23:49:21 GMT
Where is this conversation coming from? it appears to be pasted from
somewhere, who is 'we'?

params is only allowed to be one level deep anyway so it should simply be a
url-encoded string.
How is the params value passed to the server on other platforms?

The documentation simply states:
*params:* A set of optional key/value pairs to be passed along in the HTTP
request. (Object)

Does it become headers? post data? consistently across other devices?

I have reassigned the issue [3] to myself, and will address it shortly.


On Tue, Jun 19, 2012 at 3:51 PM, Filip Maj <> wrote:

> ... Currently won't work. Basically the DataContractJsonSerializer .NET
> object that we employ to parse JSON on the native side can't parse nested
> objects in JSON. The DataContract stuff is supposed to make it easy to
> cast the various JSON values to .NET types. In the case of a nested object
> with dynamic keys, that you can't model ahead of time, we tried using a
> Dictionary type on the native side. This won't work [1].
> This came up when deserializing FileTransfer upload options because they
> have a nested "params" object that house dynamic &key=value URL parameters
> to send with the HTTP request. Not sure if it happens in other spots.
> Anywho, one potential solution is to explicitly convert nested objects
> such as these to a dumber structure. In the SO thread [1] they suggest
> having an array of {key:"known1",value:"foo"} pairs replace the objects.
> The native side could parse that.
> Another option is to use the library [2]. MIT license. 300-ish kb
> .dll.
> The stock System.Json namespace that is available in .NET and has better
> capabilities is not available on Windows Phone.
> Any other solutions/ideas/comments/thoughts?
> [1]
> nknown-fields<>
> [2]


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message