> On Jan 27, 2017, at 6:31 PM, Daryle Walker <dary...@mac.com> wrote: > > Inspired by other queries on Apple APIs made of late, I spelunked GitHub to > find examples of (NS)URLSessionStreamTask. (The “NS” is dropped in Swift 3.) > Got almost nothing but hundreds of copies of AlamoFire code. I think said > code was just 100% butt coverage, and not anything useful. I found exactly > one project highlighting it, but for bad reasons. Are the problems listed at > <https://github.com/belkevich/stream-task > <https://github.com/belkevich/stream-task>> still an issue? Are there > workarounds?
[There’s seems to have been a mailing list mess-up, so I’m resending this.] The reference docs seem to have slapped in this subclass, and the guide doesn't mention it at all. The interaction model of the other tasks, prepping all the configuration then fire, doesn't fit this one. Session tasks seem to be more interactive; they can't be done-in-one. Do session tasks still use resume, or do they connect on the first read/write/TLS call? If resume is used, how would you open a connection in implicit-SSL mode? [The following wasn’t part of the original message.] That one project I found just calls “resume” and demonstrates how its delegate fails. S/he doesn’t actually provide a “real world” use of the class. For all we (developers not part of Apple) know, the bugs may be a result of not using the class correctly. — Daryle Walker Mac, Internet, and Video Game Junkie darylew AT mac DOT com
_______________________________________________ Do not post admin requests to the list. They will be ignored. Macnetworkprog mailing list (Macnetworkprog@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/macnetworkprog/archive%40mail-archive.com This email sent to arch...@mail-archive.com
