RFC: extend peerInfo

[pgte]

In peer-star-app we pass around PeerInfo objects to represent peers in apps and collaborations.
Once we introduce identity and capabilities, we need to encode and exchange this new information, and I'm thinking whether the PeerInfo objects would be the best place for this.

If yes, is there a safe extension mechanism where an app can store arbitrary information about a peer?

[satazor]

I like this idea. One possible way to ensure that those extensions do not conflict with each other is by using Symbols. The extensions would have a "getter" where you pass the PeerInfo and it would return the underlying data. For instance, getIdentity(PeerInfo) would return that symbol key's value that the identity extension created.

[pgte]

Would also love to have your input on this @alanshaw

[alanshaw]

Could you give some more info on the requirements please?

• How long does the data need to live?
• Does it need to be transferred between peers? All of it?
• What happens when the data is updated?
• Can I edit data for any peer? How do conflicts get resolved?