We demonstrate creating a peer-to-peer processing platform where multiple players function together for a common purpose: getting your work done.
MSDN Magazine June 2009
View Complete Post
Learn how you can peer-enable business applications by allowing them to share state in a serverless peer network.
MSDN Magazine July 2008
P2P applications face a number of barriers preventing their wide adoption as a productivity solution. Fortunately Windows Vista improves the situation, as you'll learn here.
MSDN Magazine October 2006
Peer-to-peer applications such as Napster, Gnutella, and Scour that communicate as peers sharing and receiving information are becoming commonplace as a means for users connected on large networks to take advantage of the vast resources available to them. The Microsoft .NET Framework provides a rich platform for building P2P apps. This article explains the concepts that make up peer-to-peer applications. The peer-to-peer application model, discovering other peers, and querying peers for information are discussed. The article goes on to cover the System.Net namespace for the use of Internet protocols, the System.Web.Services namespace for exposing Web Services, and firewall and port issues. Finally, the role of the .NET Framework in simplifying the design of powerful peer-to-peer applications is outlined.
MSDN Magazine February 2001
I was wondering if anyone knew how or seen examples on how to create 2 WPF apps that connect via IP? I saw one example
however it only works over a LAN and not the internet.
Thank a lot everyone
Am facing a problem in developing peer to peer appln.
first of all a machine has two ips(one private visible in intranet like 192.168.0.121 and second public ip visible in internet 10.2.2.3).now i need to connect to a peer located at remote place with the same criteria(two ips).The problem is i cnt go through the public ip to internal ip.On reading some articles on net i came to know the technique used to connect through public ip to private ip is termed as "HOLE PUNCHING"/"PORT FORWARDING".can some one help me on this issue? r is there any alternative other than this.I have to do it programmatically not manually.
We setup a replciation peer-to-peer source / destination has sperated publisher and distributor each.
The subscription set without initialize. But the source db got changed before replication indeed. Then we find there was something sent by destination distributor which hold all the process for a long time.
The question is: why is it not sent from source to destination? Does the destination try to question the change but very slow, and get the change back very quickly?
Under normal non-replicated circumstances, we add maintenance plans, scheduled weekly, to rebuild indexs in our SQLServer databases. We have implemented peer to peer replication to run a software project from a major application vendor and the vendor is
stating that "index maintenance plans are unsupported" in this implementation. In order to rebuild indexes, we therefore would need to break replication, rebuild indexes, then re-establish replication.
In short, can index maintenance plans be run against all nodes in a peer-to-peer replication scenario without effecting replication?
In SQL 2008 R2, I understand that Peer-to-Peer replication can provide a unique opportunity.
I'm currently looking to understand if this capability feeds into an application architecture I'm beginning to research a concept for.
My firm is a medical device manufacturer. We are looking to build a new medical device gateway. This gateway is pretty simple in that medical devices connect to the gateway to transfer device operation information (little (1000 character) XML formatted
messages, several hundred messages per minute).
In our legacy design, we have N+1 application servers, load balanced, that the medical devices communicate to. These gateway application servers send and receive XML messages to the device, and persist the messages into an Oracle 10g database (boo hiss!)
The current architecture is redundant at the application server level with load balancing, but the DB is the single point of failure.
In drawing up a concept of a new gateway, I was thinking of a design where each node of the application gateway consisted of the application services for device communications as well as MS SQL 2008 R2 Std configured as peer to peer replication between
each node (two, three, or maybe four nodes max).
So my thought was to use load balancing to have a device connect to a node in my new gateway, transmit the XML statu
Is anyone aware of an example, sample or explanation of how to do content distribution across WCF? MS mention "Content Distribution" in the docs on on peer-to-peer but I can't find a concrete example.
Most specifically, a way to handle file-sharing of large data files (> 100MB) that includes handling resumes after connections are lost.
My environment is comprising of 2 SQL servers setup with P2P replication in SQL 2008,ÃÂ 2 Web servers connect to only one SQL server at a time and make changes to the published tables andÃÂ 2 Application servers which connects to both the SQL servers all the timeÃÂ but they only read data.We chose P2P since my app servers are in different locations which read data from both the SQL servers and we use it as HA solution.Since we are changing data at only one SQL server, thought we should never get update-update conflicts but we are now on the same node.A conflict of type 'Update-Update' was detected at peer 3 between peer 1 (incoming), transaction id 0x0000000000725ca2 and peer 1 (on disk), transaction id 0x00000000007259e9 (Source: MSSQLServer, Error number: 22815)We are making changes only at Server A and Server B is my backup server.I made a varchar field updated in 1 row on a table in server A then it getsÃÂ replicated to Server Bthen I made the same field updated for 160 rows on the same table in Server A then it gets replicated to Server Bthen I reverted back the change made to the field on all 160 rows on the same table in Server A then my replication failing with Update-Update conflict.I'm not sure whats causing this because I'm not making any change
Hi, sorry but i'm a sql dummy...:-)
I setup a sql 2008 p2p replication for a database.
Can i specify, on a jbdc connection string, the path of the 2 sql server for automatic failover?
I try failoverPartner variable, but this is only for database mirroring.....
Can u help me?
Thanks in advance