Thanks for your response, I figured out that I was calling
GetUserFeedback instead of getUserFeedback. I guess I am not used to
case being an issue where urls are concerned but that is not a
problem.
With regards to node 'new', let me try to illustrate the problem
better.
In any language, if you try to unserialize json or xml you need to
have an object to map to. The problem here is since the word 'new'
is a keyword it can't be used to name a field or a property.
so if you have some json:
String jsonString = " {Messages:[{ to_user_id:134, from_user_id:4747,
new: 1 }], count:1} ";
You would have a corresponding object:
public class MessageWrapper
{
public int count;
public Message[] Message;
}
public class Message
{
public int to_user_id,
public int from_userid
public boolean new;
}
var messages = json.UnSerialize<MessageWrapper>(jsonString);
The problem is the Message class would not compile because of the
field name "new".
Therefore, if you are creating json/xml output that you intended to
have unserialized then the field names must be legal.
Even the json result wrapper object is returned as {json-result
instead of json_result which is legal. My example refers to json but
the same applies to the xml results.
I hope my explanation helps. I know that there are other people using
this api and that you can't just pull the plug on them but I think
this is something to keep in mind moving forward. For now, my only
solution is to transform your results into something that can be
serialized.
On Jun 14, 9:29 pm, Lisheng Yu <
lish...@freelancer.com> wrote:
> Hi there,
>
> Sorry for the late reply.
>
> Refer to the the getUserFeedback, I have just verified it works, please
> notice this function is User/getUserFeedback rather than the profile. Please
> double check.
>
> As for the node 'new' in the messages output, unfortunately, we could not
> change the node name in this stage, which might lead to the failure for
> others applications. I think it different from String 'new' and key word
> 'new' in Java.
>
> Let me know if you have further question.
>
> Regards,
>
> Lisheng
>