I’ve been spending some time looking into NetPeerTCP for WCF with the intention of building a peer-to-peer .NET application. Obviously managing state is something that you need to be aware of, so I’ve been looking into this: –
However, I’ve come up against a brick wall: whenever I try to create callbacks over a mesh, the calling client crashes with an error: –
“A property with the name ‘TransactionFlowProperty’ already exists”
I can’t figure out why this is happening. There appears to also be precious little material on the web about this – so if anyone has any information on this, please let me know!
Doing callbacks over a client/server architecture works fine – it’s just when it’s over the p2p mesh that it goes doolally.