csantanapr commented on issue #12: Swift SDK does not support self-signed server certificates. URL: https://github.com/apache/incubator-openwhisk-runtime-swift/issues/12#issuecomment-363085463 @jthomas >In the code above, this won't be the default behaviour. It relies on the user explictly setting a function parameter, which defaults to false. This mirrors the behaviour of the JavaScript SDK. Sorry read your comment again, I think I missed it the first time. The default behavior for what ever reason today (ie. 3.1.1) _Whisk class API is `blocking: Bool = true` different from the JavaScript SDK. https://github.com/apache/incubator-openwhisk-runtime-swift/blob/master/core/swift3.1.1Action/spm-build/_Whisk.swift#L23 ``` class func invoke(actionNamed action : String, withParameters params : [String:Any], blocking: Bool = true) -> [String:Any] { ``` It would be good to have consistency with theJavaScript SDK, but I think is more important to not break people's code by changing the API when they move from swift 3 to swift4. I think it's something to note when we get to building new Library/SDK for swift4+ both client and server, and maybe a new Class `OpenWhisk`, then I think will have an opportunity to change the API to invoke
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
