β Scribed by Matthew Macdonald (auth.)
No coin nor oath required. For personal study only.
Peer-to-peer (P2P) proponents claim that their technology holds the keys to building virtual supercomputers, sharing vast pools of knowledge, and creating self-sufficient communities on the Internet. Peer-to-Peer with VB .NET explores how these design ideas can be integrated into existing .NET applications.
This book is an honest assessment of P2P and .NET. It doesn't just explain how to create P2P applicationsβit examines the tradeoffs that professional developers will encounter with .NET and P2P. It also considers several different approaches (Remoting, .NET networking, etc.) rather than adopting one fixed technology, and includes detailed examples of several popular P2P application types (messenger, file sharer, and distributed task manager).
Front Matter....Pages i-xxvi
Front Matter....Pages 1-1
The Evolution of Peer-to-Peer....Pages 3-21
Peer-to-Peer Architecture....Pages 23-31
Front Matter....Pages 33-33
Remoting Essentials....Pages 35-69
Building a Simple Messenger....Pages 71-111
Threading the Coordination Server....Pages 113-145
Building a Distributed Task Manager....Pages 147-186
Front Matter....Pages 187-187
Networking Essentials....Pages 189-214
Building a Discovery Web Service....Pages 215-240
Building a File Sharer....Pages 241-286
Using a Discovery Service with Remoting....Pages 287-302
Front Matter....Pages 303-303
Security and Cryptography....Pages 305-333
Working with Messenger and Groove....Pages 335-363
The Intel Peer-to-Peer Accelerator Kit....Pages 365-394
Back Matter....Pages 395-412
Software Engineering/Programming and Operating Systems
π SIMILAR VOLUMES
This text takes a look at peer-to-peer programming with VB .NET, and provides complete examples demonstrating instant messaging, file sharing, and how distributed computing and peer-to-peer work together.
<p><P>Client/Server architecture was first proposed in the late 1980s as an alternative to conventional mainframe systems. Mainframe processing quickly becomes a bottleneck in any information system, but client/server models shift the processing burden to the client computer. Through workload sharin
Client/Server architecture was first proposed in the late 1980s as an alternative to conventional mainframe systems. Mainframe processing quickly becomes a bottleneck in any information system, but client/server models shift the processing burden to the client computer. Through workload sharing, cli
<P>Client/Server architecture was first proposed in the late 1980s as an alternative to conventional mainframe systems. Mainframe processing quickly becomes a bottleneck in any information system, but client/server models shift the processing burden to the client computer. Through workload sharing,