For
example, Server is a simple name; the fully qualified name of our server class
is ClientServerImpl.Server. Namespaces and fully qualified names make it possible
to avoid name conflicts where other programs use the same simple names
(Server, etc.). The namespace declaration is optional but should be used in code
that you expect will be integrated into a larger system. The using statements identify
the namespaces of other types used in the source program, so we can use their
simple names (such as Socket) rather than their fully qualified names (such as
System.Net.Sockets.Socket). During development, it is typical (but not required)
to put files that declare different namespaces in different directories. This makes it
possible to use the (short) simple names also as file names, without fear of creating
file name conflicts.
2.5 Applications
Our two application programs Monitor and Logger (Figures 2.7 and 2.8) each contain
a main method that calls methods in our libraries. The applications provide the
Overview 21
using System;
using System.Net; // Dns and IPHostEntry
namespace ClientServerImpl
{
// Remote instrument standalone server program, works with Logger client
class Monitor
{
#region usage method, writes help text (code not shown)
static void Main(string[] args)
{
string host = "127.0.0.1";
int port = 8000;
int nsessions = Int32.
Pages:
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52