Thanks.
In your original post you showed an example that isn't using JSON.
I can't reproduce your problem where JSON is not used. This server side code:
Code: Select all
ISFSObject response = new SFSObject();
response.putSFSObject("test", new SFSObject());
send("EmptyObj", response, sender);
works without issues with this client side C# code:
Code: Select all
private void OnExtensionRes(BaseEvent evt)
{
ISFSObject res = evt.Params["params"] as SFSObject;
Console.WriteLine("Test object ==> " + res.GetSFSObject("test"));
}
The object exists as SFSObject and it's not null.
As regards the example using JSON:
Code: Select all
ISFSObject a = SFSObject.NewFromJsonData(" {"test":{}} ");
I was able to reproduce the problem although this only happens in C#, and not in other languages supporting JSON.
We'll have to investigate.
As a side note I have to say that support for JSON was only introduced to support the old non-binary websocket protocol, which is now surpassed and therefore JSON support still exists for retro-compatibility but it will be dropped eventually.
Thanks