L
Laura Stern
Guest
I wasn't really thinking that specifically. Yes, input of one, output of the other should work. But I would have thought that the input-output object case would work as well, where the jsonObject property is set before returning. If it doesn't work, that seems wrong. And just to address your original question/point: Why doesn't setting the handle to your dynamically created Dataset send back all the records? First of all, for some handle types, it would be impossible to recreate the state of the handle back on the client. Take the case of a socket object, for example. So we would have to treat a TT or DataSet handle as a special case if we wanted to send back the contents/state and not just the handle value. Inconsistency is usually not a good thing. Secondly, what if we did serialize that back. On the client, we could not use the same handle value(s), as they might conflict with existing handles already there. So we'd have to create new ones. And then what if you sent that object back to the server again? Do we again serialize all the records back to the server? And if we did, once on the server, we'd again have to re-create the handles. The original copy you had there would get "lost". Is this all really what you want? So the semantics of this operation are not clear and problematic. And of course, you would lose the ability to just round-trip the handle value, which is what we do now.
Continue reading...
Continue reading...