Re: [swift-corelibs-dev] NSURLSession & libcurl

> wrote: >> - >> To: Tony Parker <anthony.par...@apple.com <mailto:anthony.par...@apple.com>> >> From: Daniel Eggert <danielegg...@me.com <mailto:danielegg...@me.com>> >> Date: 04/19/2016 08:21PM >> Cc: Pushkar N Kulkarni/India/IBM@IBMI

Re: [swift-corelibs-dev] NSURLSession & libcurl

08:21PM > Cc: Pushkar N Kulkarni/India/IBM@IBMIN, Swift corelibs dev > <swift-corelibs-dev@swift.org> > Subject: Re: [swift-corelibs-dev] NSURLSession & libcurl > > I don't think it compiles, but I haven't tried, yet. I've been trying to keep > it up-to-date with

Re: [swift-corelibs-dev] NSURLSession & libcurl

Hi Tony, Daniel, Thanks for your responses. Would it be acceptable if, for now, we check for the availability of Dispatch and conditionally compile calls to it into the current implementation of NSURLSession* (something like the  _HAS_DISPATCH__ macro used in CoreFoundation)? This would make

Re: [swift-corelibs-dev] NSURLSession & libcurl

>> To: Swift corelibs dev <swift-corelibs-dev@swift.org> >> From: Daniel Eggert via swift-corelibs-dev >> Sent by: swift-corelibs-dev-boun...@swift.org >> Date: 04/05/2016 12:14AM >> Subject: Re: [swift-corelibs-dev] NSURLSession & libcurl >> >> I

Re: [swift-corelibs-dev] NSURLSession & libcurl

Thanks for your great work on NSURLSession and friends, Daniel!I was wondering if we are only waiting for dispatch to be available on Linux here. In that case, could we have the failing tests (if any) excluded (only on Linux perhaps) and have this merged please? Some of us at IBM would like to

Re: [swift-corelibs-dev] NSURLSession & libcurl

Changes since last week: NSURLSessionDataTask (i.e. GET requests) now work with callbacks and with completion handler. Debug output is enabled by environment variables. Handling a few common error scenarios to return the corresponding NSError. /Daniel

Re: [swift-corelibs-dev] NSURLSession & libcurl

> On 14 Mar 2016, at 18:29, Robert Stephen Thompson > wrote: > > Just a couple of tips based on my experience wrapping libxml2 for > NSXMLDocument: > 1. You’ll need to actually import and link libcurl with CoreFoundation > instead of trying to make a

Re: [swift-corelibs-dev] NSURLSession & libcurl

Awesome, thanks for taking this on! - Tony > On Mar 17, 2016, at 12:33 PM, Daniel Eggert via swift-corelibs-dev > wrote: > > I’ve made good progress on this. I’ll try to get something that’s merge-able > within the next week. It won’t be 100% complete by any

Re: [swift-corelibs-dev] NSURLSession & libcurl

That seems pretty reasonable to me, I guess the only thing to watch out for is private vs internal. Sent from my iPhone > On Mar 15, 2016, at 2:44 AM, Daniel Eggert wrote: > > Is it ok for me to split the libcurl specific code inside Foundation into a > separate file,

Re: [swift-corelibs-dev] NSURLSession & libcurl

Is it ok for me to split the libcurl specific code inside Foundation into a separate file, say NSURLSession+curl.swift ? Or should I try to keep everything inside NSURLSession.swift ? If I go for a separate file, I'd be able to differentiate between internal and private for the helpers. I'll