Re:Show HN: Swift SOAP Client library through code generation
by joelhaasnoot on Tuesday February 21, 2017 @01:34PM
(#13698086)
I pitty anyone writing direct SOAP interfaces for an iOS app.
From a few years of app dev, at the end of the day it makes everthing a lot more flexible if proxied, even with a tiny facade, because it gives you options and choices when it comes to making changes.
Re:Show HN: Swift SOAP Client library through code generation
by bouke on Tuesday February 21, 2017 @02:48PM
(#13699136)
Sure it might not make sense to use SOAP for communication between an iOS app and its server-side counterpart. However when writing consumers of an existing SOAP service, for example in an macOS or console application; it might make more sense.
Re:Show HN: Swift SOAP Client library through code generation
by wing328hk on Monday February 27, 2017 @02:21AM
(#13742488)
If anyone is looking for an auto-generated Swift REST client, please give Swagger Codegen [1] a try and the latest master supports both Swift 2.x and 3.
Re:Show HN: Swift SOAP Client library through code generation
by drmohundro on Tuesday February 21, 2017 @06:08PM
(#13701074)
This looks great - I was working with an old iOS app back when Swift was first released and I wrote an XML parsing library SOLELY because the SOAP support was horrific. I think this will help a lot of people. If you don't mind, I might add a link to your repo from my README just to help point people towards a better approach over manual XML parsing.
Re:Show HN: Swift SOAP Client library through code generation
by mvantellingen on Tuesday February 21, 2017 @06:06PM
(#13701061)
Cool! As the author of a relative new python soap client (zeep) i do feel sorry for you Most wsdl documents dont follow the various specs which will result in a lot of support issues from users
Anyway feel free to contact me if you have any spec related questions
Re:Show HN: Swift SOAP Client library through code generation
by bouke on Wednesday February 22, 2017 @01:57AM
(#13703683)
Cool project, seems like a nice improvement over what I've used in the past (suds). Also has some features that Lark currently lacks (SOAP 1.2 / HTTP bindings / rpc / WS-Addressing / WSSE).
From a few years of app dev, at the end of the day it makes everthing a lot more flexible if proxied, even with a tiny facade, because it gives you options and choices when it comes to making changes.
[1]: https://github.com/swagger-api/swagger-codegen
Disclaimer: I'm a top contributor to the project.
Anyway feel free to contact me if you have any spec related questions