Distributed .NET Programming in CSharp
The subject of distributed programming is vast. To implement distributed applications properly, you must understand everything from low-level networking details to high-level architectural issues. .NET is a brand new platform deserving of several thousand pages of documentation. So the challenge I f...
Đã lưu trong:
| Tác giả chính: | |
|---|---|
| Định dạng: | Sách |
| Ngôn ngữ: | English |
| Được phát hành: |
Apress
2012
|
| Những chủ đề: | |
| Truy cập trực tuyến: | https://scholar.dlu.edu.vn/thuvienso/handle/DLU123456789/30993 |
| Các nhãn: |
Thêm thẻ
Không có thẻ, Là người đầu tiên thẻ bản ghi này!
|
| Thư viện lưu trữ: | Thư viện Trường Đại học Đà Lạt |
|---|
| Tóm tắt: | The subject of distributed programming is vast. To implement distributed applications properly, you must understand everything from low-level networking details to high-level architectural issues. .NET is a brand new platform deserving of several thousand pages of documentation. So the challenge I faced when writing this book was this: how do I combine these two immense subjects into a single, digestible volume?
My answer: I don't. In other words, I had to make assumptions regarding the level of experience of the reader, which is tough given that .NET is such a new technology. Even harder, though, I had to make difficult decisions about what the book would and would not be. On a few issues I was resolute. The book would not be a regurgitation of documentation. The book would not be a thousand-page boat anchor covering dozens of subjects and none of them well.
Rather than list other things this book is not, however, I want to discuss what this book is. I think of it as a guided tour through the fundamental technologies you use to build distributed applications with .NET, such as .NET Remoting, Web services, serialization, COM+, and MSMQ. These technologies are the tools we developers use to craft distributed applications. And they are complex enough in themselves to warrant in-depth examination. The focus, then, is on the use of each technology and the role it plays in a distributed application. Think of it as pulling each tool out of the box, examining it, and experimenting with it to get a sense of the problems it can solve. Like any craft, distributed programming is best learned by doing, but wherever possible I discuss the pros and cons of using one tool over another. |
|---|