1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
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
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
<HEAD><style> A { color:black }</style>
<!-- hennerik CVSweb $Revision: 1.93 $ -->
<TITLE>code/nel/doc/nel_samples.dxt - view - 1.3</TITLE></HEAD>
<BODY BGCOLOR="#eeeeee">
<table width="100%" border=0 cellspacing=0 cellpadding=1 bgcolor="#aaaaaa"><tr valign=bottom><td><a href="nel_samples.dxt?sortby=rev"><IMG SRC="http://www.nevrax.org/inc/img/picto-up.gif" ALT="[BACK]" BORDER="0" WIDTH="14" HEIGHT="13"></a> <b>Return to <A HREF="nel_samples.dxt?sortby=rev">nel_samples.dxt</A>
CVS log</b> <IMG SRC="http://www.nevrax.org/inc/img/picto-news.gif" ALT="[TXT]" BORDER="0" WIDTH="13" HEIGHT="15"></td><td align=right><IMG SRC="http://www.nevrax.org/inc/img/picto-dir.gif" ALT="[DIR]" BORDER="0" WIDTH="15" HEIGHT="13"> <b>Up to <a href="/cvs/cvsweb.cgi/?sortby=rev">Nevrax</a> / <a href="/cvs/cvsweb.cgi/code/?sortby=rev">code</a> / <a href="/cvs/cvsweb.cgi/code/nel/?sortby=rev">nel</a> / <a href="/cvs/cvsweb.cgi/code/nel/doc/?sortby=rev">doc</a></b></td></tr></table><HR noshade><table width="100%"><tr><td bgcolor="#ffffff">File: <a href="/cvs/cvsweb.cgi/?sortby=rev">Nevrax</a> / <a href="/cvs/cvsweb.cgi/code/?sortby=rev">code</a> / <a href="/cvs/cvsweb.cgi/code/nel/?sortby=rev">nel</a> / <a href="/cvs/cvsweb.cgi/code/nel/doc/?sortby=rev">doc</a> / <a href="/cvs/cvsweb.cgi/code/nel/doc/nel_samples.dxt?sortby=rev">nel_samples.dxt</a> (<A HREF="/cvs/cvsweb.cgi/~checkout~/code/nel/doc/nel_samples.dxt?rev=1.3&sortby=rev" target="cvs_checkout" onClick="window.open('/cvs/cvsweb.cgi/~checkout~/code/nel/doc/nel_samples.dxt?rev=1.3','cvs_checkout','resizeable,scrollbars');"><b>download</b></A>)<BR>
Revision <B>1.3</B>, <i>Tue Apr 16 13:54:27 2002 UTC</i> (3 months ago) by <i>lecroart</i>
<BR>Branch: <b>MAIN</b>
<BR>CVS Tags: <b>georges_v2, HEAD</b><BR>Changes since <b>1.2: +14 -12
lines</b><PRE>
ADDED: description
</PRE>
</td></tr></table><HR noshade><PRE>/**
\page nelsamples NeL Samples
$Id: nel_samples.dxt,v 1.3 2002/04/16 13:54:27 lecroart Exp $
\author Olivier Cado, Vianney Lecroart
\date 06/15/2001
\section samisc NeL Misc Samples
Theses samples illustrates the usage of the miscellaneous library. This is the based library used by all other Nevrax libraries.
It contains all usefull class and features that are not specific for one or another library.
\subsection samisccommand command
This samples describes how to create commands and execute them using ICommand class. It's a generic system to create and execute
command at run time (it is used in all services, snowballs client and so on).
\subsection samiscconfigfile configfile
This samples describes how to use NeL configuration file. (This system is used in all services, snowballs client and so on).
\subsection samiscdebug debug
This program shows you how to use basic debug stuffs that are used everywhere in NeL.
\subsection samisclog log
This sample uses the log and displayer system that is a generic way to generate output (on screen, file, network and so one).
\section sanetwork NeL Net Samples
Theses samples illustrate the usage of network library
\subsection sanetlogin_system login_system
This examples shows you how to use the login system provided by NeL to connects/check/identify clients.
\subsection sanetservice service
This is a very simple service example to describes the architecture to create services.
\subsection sanetlayer3 net_layer3
This project demonstrates the usage of layer 3 (NLNET::CCallbackClient, NLNET::CCallbackServer) and the
service framework (NLNET::IService). It contains three programs: a client, a front-end service and a ping service.
- The client connects to a front-end server at localhost:37000.
It sends pings and expects pongs (ping replies).
- The front-end server expects pings, and forward them to
the real ping server (known as "PS" in the naming service).
When the ping server sends a pong back, the front-end server forwards it to the client.
- The ping service (PS) expects pings and sends pongs back.
To run the front-end service and the ping service, ensure
their config files, frontend_service.cfg and ping_service.cfg,
are located in the directory where they are run. These files
state the address of the naming service.
\subsection sanetlayer4 net_layer4
This project demonstrates the usage of layer 4 (NLNET::CNetManager), the
service framework (NLNET::IService), and the connection and disconnection callbacks.
It contains three programs: a client, a front-end service and a ping service.
The functionalities are close to the ones of the previous sample.
- The client connects to a front-end server at localhost:37000.
It sends pings and expects pongs (ping replies).
- This front-end server expects pings, and forward them to
the real ping server. When the ping server sends a pong back,
the front-end server forwards it to the client.
Even if the connection to the ping server is broken, our
front-end server will keep storing the ping messages and
will forward them when the connection is restored, thanks
to layer 4.
- The ping service (PS) expects pings and sends pongs back.
To run the front-end service and the ping service, ensure
their config files, frontend_service.cfg and ping_service.cfg,
are located in the directory where they are run. These files
state the address of the naming service.
\subsection sanetlayer5 net_layer5
This project demonstrates the usage of layer 5 (NLNET::CUnifiedNetwork), the
service framework (NLNET::IService), and the connection and disconnection callbacks.
It contains a set of services that communicate between them.
The functionalities are close to the ones of the previous sample but they add some
features like unified callback array, and so on.
\subsection sanetudp udp
This project demonstrates the usage of a client/server architecture for
benching an UDP connection. The server listen on TCP port and UDP port
for new incoming client. When a client is connected, it communicates on
the TCP port to set the bench and after it uses the UDP port to bench the
connection. The server log information on text file and send some info on
the client using the TCP connection.
\subsection sanetclasstransport class_transport
This project demonstrates the usage of the CTransportClass class.
This class allows services to send easily some class to another service.
It manages different class version (For example, the sender class can have
different variables than the receiver class)
\section sa3d NeL 3D Samples
\e Document \e under \e construction
\subsection sa3dfont font
\e Document \e under \e construction
\section sapacs NeL PACS Samples
\e Document \e under \e construction
\section saai NeL AI Samples
\e Document \e under \e construction
*/</PRE>
|
