blob: fe9c6a194f89c6bd150b6e189b6b3d3d3c9d657b (
plain)
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
149
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Nel] More news from the nevrax teams...</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:alfred%40mazuma.net.au">
<LINK REL="Previous" HREF="000427.html">
<LINK REL="Next" HREF="000429.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Nel] More news from the nevrax teams...</H1>
<B>Alfred</B>
<A HREF="mailto:alfred%40mazuma.net.au"
TITLE="[Nel] More news from the nevrax teams...">alfred@mazuma.net.au</A><BR>
<I>Thu, 21 Jun 2001 21:48:35 +1000</I>
<P><UL>
<LI> Previous message: <A HREF="000427.html">[Nel] More news from the nevrax teams...</A></li>
<LI> Next message: <A HREF="000429.html">[Nel] More news from the nevrax teams...</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#428">[ date ]</a>
<a href="thread.html#428">[ thread ]</a>
<a href="subject.html#428">[ subject ]</a>
<a href="author.html#428">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>I have a question about the caching for the naming service. You say it
automatically corrects caches when services move or are deleted. This
doesn't sound very scalable, it every client querying the name server
has to be contacted when something they asked about changed (especially
over high latency links).
Cedric Valignat wrote:
><i>
</I>><i>
</I>><i> Network
</I>><i> -------
</I>><i>
</I>><i> - Modified behaviour of service main loop to avoid exploding input buffers.
</I>><i> The user 'update' callback is now not called until all incoming messages
</I>><i> have been processed.
</I>><i>
</I>><i> - Improved responsiveness of API for naming service
</I>><i> Each service now keeps a local cache of the addressses stored by the naming
</I>><i> service. They are automaticaly updated whenever new services are registered
</I>><i> with, or old services removed from, the naming service. This means that the
</I>><i> API never needs to contact the naming service in order to find addresses.
</I>><i>
</I>><i> - The message type compression has been dissabled
</I>><i> An automatic system made string/ uint32 associations for message types that
</I>><i> were repeatedly sent from one executable to another, so that the uint32
</I>><i> value could be sent in place of the string.
</I>><i> This system was causing problems (due to a specification problem) and has
</I>><i> been removed.
</I>><i> An alternative compression mechanism will be implemented later.
</I>><i>
</I>><i> - New example for using 'login system'
</I>><i> It can be found in the samples directory
</I>><i>
</I>><i> - Improved performance of log messages
</I>><i> Under Windows services are now Win32 applications which means that large
</I>><i> numbers of log messages no longer bring the system to its knees
</I>><i>
</I>><i> - On a transformer les services en appli Win32 pour des raisons de
</I>><i> performance. les log sont maintenant dans un fenetre Win32 au lieu d une
</I>><i> console "DOS" (commite la semaine prochaine)
</I>><i>
</I>><i> - New debugging aid
</I>><i> There is a new system for recording all of the input to a service in
</I>><i> situation and for playing back the input to the same application running
</I>><i> stand alone. This allows the application to be traced, etc.
</I>><i> The system will go up on CVS within the next few days
</I>><i>
</I>><i>
</I>><i> PACS
</I>><i> ----
</I>><i>
</I>><i> - First version of path finding functional (still requires work), Windows only
</I>><i> at the moment.
</I>><i>
</I>><i>
</I>><i> 3D
</I>><i> --
</I>><i>
</I>><i> - The header file have moved!
</I>><i> The private header files are in the /nel/src/3d tree (allong with their
</I>><i> respective source files)
</I>><i> The public include files are now in nel/include/nel/3d
</I>><i>
</I>><i> - System for generating object positions on the landscape completed
</I>><i> This system works out which patch the object is attached to and the position
</I>><i> within the patch. It then generates a 3D world position based on the patch
</I>><i> tesselation. Objects using this system will stay attached to the ground
</I>><i> regardless of the level of detail that the landsacep is displayed at.
</I>><i>
</I>><i> - In development...
</I>><i> Light maps for interiors, collisions (for interiors and exteriors) and the
</I>><i> editor for the particle system are in development.
</I>><i>
</I>><i>
</I>><i> Audio
</I>><i> -----
</I>><i>
</I>><i> - Work is starting on the audio library.
</I>><i> During the next couple of months we will develop the base of the system and
</I>><i> a Direct Sound driver implementation. We will have a look at doing an OpenAL
</I>><i> diver in the autumn.
</I>><i>
</I>><i>
</I>><i> AI
</I>><i> --
</I>><i>
</I>><i> - Silence from the AI team
</I>><i> The AI team are plunged into product specific code right now. There will be
</I>><i> little news from them for a few months
</I>><i>
</I>><i>
</I>><i>
</I>><i> _______________________________________________
</I>><i> Nel mailing list
</I>><i> <A HREF="mailto:Nel@nevrax.org">Nel@nevrax.org</A>
</I>><i> <A HREF="http://www.nevrax.org/mailman/listinfo.cgi/nel">http://www.nevrax.org/mailman/listinfo.cgi/nel</A>
</I>><i>
</I>
--
Alfred Reynolds
<A HREF="mailto:alfred@mazuma.net.au">alfred@mazuma.net.au</A>
</pre>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI> Previous message: <A HREF="000427.html">[Nel] More news from the nevrax teams...</A></li>
<LI> Next message: <A HREF="000429.html">[Nel] More news from the nevrax teams...</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#428">[ date ]</a>
<a href="thread.html#428">[ thread ]</a>
<a href="subject.html#428">[ subject ]</a>
<a href="author.html#428">[ author ]</a>
</LI>
</UL>
</body></html>
|
