<story><title>Deciphering the Messages of Apple’s T2 Coprocessor</title><url>https://duo.com/labs/research/apple-t2-xpc</url></story><parent_chain><item><author>AlphaWeaver</author><text>Why did Apple choose to use a networking protocol like HTTP to interface with two chips in the same hardware device?</text></item></parent_chain><comment><author>nimish</author><text>The amount of money and eyeballs testing out an http stack far exceed that of a proprietary protocol.&lt;p&gt;The real question is why don&amp;#x27;t more rpc style protocols just use http?</text></comment>
<story><title>Deciphering the Messages of Apple’s T2 Coprocessor</title><url>https://duo.com/labs/research/apple-t2-xpc</url></story><parent_chain><item><author>AlphaWeaver</author><text>Why did Apple choose to use a networking protocol like HTTP to interface with two chips in the same hardware device?</text></item></parent_chain><comment><author>therein</author><text>Apple tends to do that a lot. Back when I worked at Apple I had noticed the same thing. Two services that are sharing memory end up communicating over HTTP and I always found it silly.</text></comment>