<div dir="ltr">Hello,<div><br></div><div>From a serval perspective, we don't need a true IP mesh, as we can use any underlying transport on which to run our overlay.  So for us it is potentially a big step forward.</div>
<div><br></div><div>Paul.</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Mar 24, 2014 at 11:08 AM, Nathan of Guardian <span dir="ltr"><<a href="mailto:nathan@guardianproject.info" target="_blank">nathan@guardianproject.info</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On 03/23/2014 08:07 PM, Paul Gardner-Stephen wrote:<br>
> <a href="http://www.cultofmac.com/271225/appreciated-ios-7-feature-will-change-world/" target="_blank">http://www.cultofmac.com/271225/appreciated-ios-7-feature-will-change-world/</a><br>
><br>
> This is very significant.  I have poked my contact in the Android team at<br>
> Google to see if they have any comment, as Apple is now well ahead of<br>
> Android in terms of this functionality.<br>
<br>
</div></div>Isn't that article a bit over stating what the Multipeer Connectivity<br>
framework provides? Isn't the framework more like a super-bonjour, then<br>
a full-fledged IP mesh?<br>
<br>
Based on what I am reading here:<br>
<a href="https://developer.apple.com/library/ios/documentation/MultipeerConnectivity/Reference/MultipeerConnectivityFramework/Introduction/Introduction.html" target="_blank">https://developer.apple.com/library/ios/documentation/MultipeerConnectivity/Reference/MultipeerConnectivityFramework/Introduction/Introduction.html</a><br>

<br>
it seems that way.<br>
<br>
The only that seems new to me is that you can use it over Bluetooth<br>
without specifically having to pair... is it also somehow automatically<br>
using adhoc wifi?<br>
<span class="HOEnZb"><font color="#888888"><br>
+n<br>
</font></span></blockquote></div><br></div>