MICROSOFT_PRESS_EBOOK_PROGRAMMING_WINDOWS_8_APPS_WITH_HTML_CSS_AND_JAVASCRIPT_PDF

From this point on, you’re free to send whatever data with whatever protocols you’d like, on the
assumption, of course, that the app on the other end will understand what you’re sending. This is clearly
not a problem when it’s the same app on both ends of the connection; different apps, of course, will
need to share a common protocol. In the sample, the “protocol” exchanges only some basic values, but
the process is all there.
If at any time you want to stop advertising, call PeerFinder.stop. To close a specific connection, call
the socket’s close method.
Making a Connection
On the other side of a proximity relationship, an app can look for peers that are advertising themselves
over WiFi Direct or Bluetooth. In the Proximity sample, a Browse Peers button is enabled if the browse
discovery type is available. This button triggers a call to the following function (js/PeerFinder.js) that
uses PeerFinder.findAllPeersAsync to populate a list of possible connections, including those from
different apps:
function peerFinder_BrowsePeers() {
// Empty the current option list [code omitted]
}
ProxNS.PeerFinder.findAllPeersAsync().done(function (peerInfoCollection) {
// Add newly found peers into the drop down list.
for (i = 0; i < peerInfoCollection.size; i++) {
var peerInformation = peerInfoCollection[i];
// Create and append option element using peerInformation.displayName
// to the peerFinder_FoundPeersList control [code omitted]
}
});
When you select a peer to connect to, the sample takes its PeerInformation object and calls
PeerFinder.connectAsync as before (during which the user is prompted for consent):
function peerFinder_Connect() {
var foundPeersList = ProximityHelpers.id("peerFinder_FoundPeersList");
var peerToConnect = discoveredPeers[foundPeersList.selectedIndex];
}
ProxNS.PeerFinder.connectAsync(peerToConnect).done(
function (proximitySocket) {
startSendReceive(proximitySocket);
});
Once again, this provides a StreamSocket as a result, which you can use as you will. To terminate the
connection, call the socket’s close method.
704