“smb big sur”

OK, lots of points to cover here:I’ve moved your thread to Core OS > Networking as this question is more about networking than it is about Swift.If you’re writing new code you should use NSURLSession rather than NSURLConnection; we’re in the process of deprecating the latter in favour of the former.You should read up on App Transport Security because that’s likely to impact on your product in the very near future.Error -9813 is errSSLNoRootCert, implying that you really do have an HTTPS server trust evaluation problem. Technote 2232 HTTPS Server Trust Evaluation covers that topic in detail.You’re calling NSURLConnection synchronously (using the +sendSynchronousRequest:xxx method). This is a bad idea in general for all sorts of reasons. I strongly recommend that you move to an async API. In fact, if you switch to NSURLSession you’ll find that it has no sync API.With regards your attempted solution, the problem you’re having is that -connection:willSendRequestForAuthenticationChallenge: is an NSURLConnection

Oh, It's really bad !I also use the long waiting time to make screenshots !It's a big hurt for individual developer !

Other than reuse of a custom view, which I rarely run into needing, what flexibility are you losing? I never use XIB any longer because storyboard makes things so much easier for me, and now that they finally let us use references to other storyboards, the main complaint I had about them is gone (They could get too big)

Same build; I usually just copy-drag the project folder, with the Build folder deleted, from my Yosemite machine to my El Capitan one when I want to switch environments. I target 10.10 on both machines. The only differences should be the Xcode and SDK versions.I'll file a bug. Going to Metal on El Capitan is a big change and I expected some problems, but this one is so visible and basic to SceneKit that my immediate thoughts were I can't be the only persone seeing this so I must be doing something wrong in how I create the objects.Thanks for the reply.

Perhaps I could have said this more clearly: The way that Apple set up Open Directory within OS X Server is very much like the Windows NT domain services. OS X Server can be set up as an Open Directory master, or as a replica. Active Directory domain controllers use multi-master replicatiom, so there can be multiple primaries on the network, each having a read/write copy of the directory database.You are right that the cloud is becoming an integral part of networking, however, there is still a place for locally-hosted servers, so corporate datacenters will still be used by some people.IN much the same way that Apple has moved from its AFP-based file sharing protocols to Microsoft's SMB protocol, OS X Server should move away from Open Directory, and move toward Active Directory. The SAMBA project has built AD comain controller functionality into version 4 of their suite, so if this is possible with open-source software, then Apple may be in a position to do the same thing with their server so

Just wait 'till they make the iTunes dock icon twice as big as everything else...

Heya, Hmmmm,I suppose that would be possible during development, ( of which i have almost finished now anyway) However my goal is produce a tool that users/customers could use when they have systems with multiple cards.Also i'm not big on the idea of duplicating an entire kext, just so that i can disable 1 of 2 or 3 when i need to.But given the lack of responses on here I'm starting to think it's just not possible? 😟Thanks for the reposnse anyway

I was afraid of that, but I was able to work around it with a re-design. It ended up being not that big of a deal for me, but still I was disappointed!