locked
Direct Connect via Mesh Pattern? RRS feed

  • Question

  •  

    Hi folks,

     

    I'm wondering if anybody on the P2P team (or anybody at all) has identified and documented somewhere either a pattern or best practice for direct connect via the mesh?

     

    The situation I'm concerned with is the following.

     

    Node A and B are different clients connected to the same mesh.  Node A broadcasts a message to all clients on the mesh.  Node B receives the message and wishes to respond with a message directly to Node A without broadcasting. 

     

    Is there an architectural best practice to do this on the same mesh?  Should a private mesh be instantiated and used with only Node A and Node B as members?  Should Node A include in its broadcast connection details for a direct TCP connection?  Etc etc.

     

    What do you guys do when you need to address this situation?

     

    Regards,


    Roland Rodriguez

    Wednesday, February 6, 2008 9:01 PM

All replies

  • any updates on this anybody? 

    thx,

    -r
    Wednesday, February 11, 2009 8:08 PM
  • It would help to know what kind of p2p infrastructure you're using.  From what you wrote, it seems like you're developing one from scratch.  Either way, direct communication between peers in a mesh is a common scenario, and can be handled in a variety of ways - tcp, udp, a broadcast that only the recipient can accept.  Your idea of a private mesh would be interesting for a subset mesh of peers, but is probably overly complex for 1:1 communication.

    You might want to take a look at Windows P2P Graphing and Grouping, mesh protocols that implement direct connections between two peers.

    The PeerChannel framework uses a different pattern and lets the developer implement various filtering heuristics on broadcast messages to simulate direct connections.

    Hope that helps,
    Vladimir

    This posting is provided "AS IS" with no warranties, and confers no rights
    Thursday, February 12, 2009 8:24 AM