Is this a P2P app?
Interresting application brewing here. I'll paint you a version of the picture using a made up scenario so you don't have to deal with the industry specific mumbo-jumbo of the actual problem.
Picture the typical home weather station. An individual station provides several different measurements of the weather: temperature, humidity, wind speed, barometric pressure, etc.
The world is filled with such stations - there may infact at some point be one in every home, business, etc.
As a weather geek, I'd like to get access to the data on some of these stations, but probably not all of them. I may also be interrested in the data from different stations (perhaps even down to the measurement level) at different rates. The temperature at my neighbors house I want to know every second, but the temperature in Bermuda maybe only once per hour.
I'm picturing some sort of a decentralized directory system (similar to AD with its multi-master characteristics) to keep track of all these stations. Then, a P2P network using a pub/sub model to initiate communications. Finally, use a streaming media like protocol (complete with IP multicast) to fill the subscriptions so that there aren't really 10,000,000 connections to the popular sites (like the top of Mt. Everest which will be stuck using satelite for bandwidth).
Now for the catch, the data rates in my made up scenario using weather stations would be relatively low. My real app is talking to meters that take measurements at up to 100 times / second. It gets worse, not only are the data rates high (data packet size is manageable though), but latency is a killer.
Just curious what the group thought.
Also, if you think I'm on the right track here - give me your thoughts on how usable WCF is in this scenario.
Thanks,
Matt
