realberen - Currently it doesn't handle sending complex objects as part of the message, it can just receive them. (that's all I needed for my app, so I didn't take it that far). The REST handling is built in on the ASP.NET side, so if you can figure out the parameter names it expects for these complex objects, I don't see any reason why you couldn't create a generic method to convert your XCode objects into those parameters.
wtyphoon - Definitely no base 64 support either. Although you should receive the string value back and be able to decode it in the XCode.
As far as whether it's better to take this approach or just call rest and handle it manually for each web service call, it was a no-brainer for me. It's a royal pain to deal with three different methods to receive the open tag, close tag and contents, and keep track of all your nesting to and build out your object tree. The missing "built-in" classes provide you with a nice object tree instead of the series of methods which is FAR easier to convert into your custom objects. That's what I set out to replicate here.
I'm still absolutely shocked Apple would leave this core functionality on a platform made for developing web connected mobile apps. I'm still holding out hope this will eventually be added. In theory, once it is, I can just swap out this code for the built-in libraries without having to change all my code that converts the result into my custom objects.
|
