Re: Crazy???, big picture questions.
Re: Crazy???, big picture questions.
- Subject: Re: Crazy???, big picture questions.
- From: Josh Graessley <email@hidden>
- Date: Thu, 02 Aug 2012 15:40:55 -0700
Use the highest layer you can. It the highest layer, you can tell the system more about what you're trying to do (fetch the resource at the URL X). At the lower layers, the system has no idea what you're really trying to accomplish, so it can't help you with anything.
Security is, in some respects, much easier if you have a big server in the sky with a valid certificate. HTTPs is already supported by the system and the default certificate verification is often sufficient for most needs. HTTP has no security, everything is in the clear. If security is a concern, you must tunnel HTTP on top of TLS or SSL (https).
Quinn put together an excellent set of presentations at the 2010 WWDC. If you haven't had a chance to watch those yet, I would strongly encourage you to do so.
I'm sorry if this years presentation caused confusion. We have seen performance problems with various applications. We wanted to show illustrate the lower layers work and follow that with advice on what to do at the higher layers. We didn't want to jump straight to "use http pipeling" without explaining why first.
-josh
On Aug 2, 2012, at 3:25 PM, Kevin Bracey <email@hidden> wrote:
> I'm not sure if this is an ok question for this list, if not please feel free to email me directly.
>
> I've been speed learning networking and studying examples. and I have 2 questions.
> Is it better to use the highest API or the lowest. Some examples work their way up, BSD > Core Foundation > Cocoa, This gives a strange mix. While others try and do it all in Cocoa. There seems to be very mixed messages in the WWDC vids. Early on the message was use the highest layer, but this year it was all about Sockets and Core Foundation. So I'm confused.
>
> Could someone please briefly explain the advantages and disadvantages of using each layer?
>
> My next pondering is again based on my wider ignorance.
> It is put forward that we can use HTTP to get a lot of security and other things for "free", but the example RemoteCurrency has no mention of these layers, and seems focused of robust lower level communication.
> Am I correct in thinking that the RemoteCurrency example is ideal for an App where the devices on the network need to chat back and forth, while HTTP is more for a main device/server handing out data with limited back and forth.
>
> Could someone please explain the advantages and disadvantages of using these different approaches
>
> Again apologies if this isn't the best place to ask, any books or references would be gladly accepted.
> I have a pressing need for a robust networking solution, that I can understand and maintain, and trying to teach an old dog new tricks.
>
> cheers
> Kevin
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Macnetworkprog mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden