eLLoco
Member | Редактировать | Профиль | Сообщение | Цитировать | Сообщить модератору
Можно также использовать COM+ с .NET, ищи информацию по System.EnterpriseServices. Но это принято считать устаревающей технологией (deprecated), по крайней мере так пишут в книжках по .NET.
Поэтому ищи лучше информацию по .NET Remoting (в сети есть отличная книга, посвященная полностью этой теме, она вроде так и называется, "Microsoft.NET Remoting"):
Цитата:
The .NET base class libraries shipped with the .NET remoting layer, represented by
the System.Runtime.Remoting namespaces. This API allows multiple computers to distribute
objects, provided they are all running the applications under the .NET platform.
The .NET remoting APIs provided a number of very useful features. Most important was the
use of XML-based configuration files to declaratively define the underlying plumbing used by the
client and the server software. Using *.config files, it was very simple to radically alter the functionality of your distributed system simply by changing the content of the configuration files and restarting the application.
As well, given the fact that this API is useable only by .NET applications, you can gain various
performance benefits, as data can be encoded in a compact binary format, and you can make use of the Common Type System (CTS) when defining parameters and return values. While it is possible to make use of .NET remoting to build distributed systems that span multiple operating systems (via Mono, briefly mentioned in Chapter 1 and detailed in Appendix B), interoperability between other programming architectures (such as J2EE) was still not directly possible.
|
После выхода в свет .NET 3.0 (или может 3.5), появилось еще более рекомендуемое Microsoft решение для распределенных приложений - WCF (Windows Communication Foundation):
Цитата:
WCF is a distributed computing toolkit introduced with .NET 3.0 that integrates these previous
independent distributed technologies into a streamlined API represented primarily via the System.ServiceModel namespace. Using WCF, you are able to expose services to callers using a wide variety of techniques. For example, if you are building an in-house application where all connected
machines are Windows based, you can make use of various TCP protocols to ensure the fastest
possible performance. This same service can also be exposed using the XML web service–based protocol to allow external callers to leverage its functionality regardless of the programming language or operating system.
Given the fact that WCF allows you to pick the correct protocol for the job (using a common
programming model), you will find that it becomes quite easy to plug and play the underlying
plumbing of your distributed application. In most cases, you can do so without being required to
recompile or redeploy the client/service software, as the grungy details are often relegated to application configuration files (much like the older .NET remoting APIs).
|
Да, в итоге имеем holy mess, и чтобы что-то выбрать, надо провести не один день читая доки и экспериментируя. Но если делаешь трехзвенку, дело видно серьезное и можно потратиться на выбор лучшего решения. Посоветую еще книжку - Apress Pro CSharp 2008 and the .NET 3.5 Platform, Fourth Edition by Andrew Troelsen. Также можно найти в сети, все цитаты приведены из нее, кстати. |
). Так что смотри, думай, вибирай, что больше подходит. 