JBYung - Initial Commit. Doesn't have anything related to iBeacon but has the Peer-2-Peer stuff. A few points to note about the initial commit:

1. The core classes are the BrowseService and AdvertiseService classes
2. The sample app allows the user to choose between 2 modes: Advertiser or Receiver. There's a UI view controller for each mode (AdvertiserViewController, BrowserViewController)
3. The current flow of the Peer 2 Peer is the following:
    - Advertiser advertises
    - If there's any "browser" out there, the browser will locate the advertiser and send an invitation to the advertiser (invitation to join the same session)
    - The advertiser will get the invitation. Currently the app provides the ability to accept/reject the invitation through a UIAlertView. However, we could set it to "accept" or "reject" by default. To achieve this, within the "AdvertiserViewController::didReceiveInvitationFromPeer" method, instead of popping a UIAlertView, pass the default flag (YES or NO) to the invitation handler block
    - If the advertiser accepts the invitation, a certificate will be generated and will be sent back to the browser. The browser will acknowledge the certificate (done in the "BrowserService::didReceiveCertificate" routine)
4. Once a session has been set up, the advertiser can sends messages to the Browser through the chat UI. We could extend this by allowing the Browser to send messages back. TBD
5. Messages strings are just an example. Essentially, we could serialize anything and send it from one peer to another within the session. The key here is to get the peers within the same session