diff options
| author | neodarz <neodarz@neodarz.net> | 2018-08-11 20:21:34 +0200 |
|---|---|---|
| committer | neodarz <neodarz@neodarz.net> | 2018-08-11 20:21:34 +0200 |
| commit | 0ea5fc66924303d1bf73ba283a383e2aadee02f2 (patch) | |
| tree | 2568e71a7ccc44ec23b8bb3f0ff97fb6bf2ed709 /pipermail/nel/2001-February/000231.html | |
| download | nevrax-website-self-hostable-0ea5fc66924303d1bf73ba283a383e2aadee02f2.tar.xz nevrax-website-self-hostable-0ea5fc66924303d1bf73ba283a383e2aadee02f2.zip | |
Initial commit
Diffstat (limited to '')
| -rw-r--r-- | pipermail/nel/2001-February/000231.html | 106 |
1 files changed, 106 insertions, 0 deletions
diff --git a/pipermail/nel/2001-February/000231.html b/pipermail/nel/2001-February/000231.html new file mode 100644 index 00000000..110c8aea --- /dev/null +++ b/pipermail/nel/2001-February/000231.html @@ -0,0 +1,106 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Nel] Dynamic load balancing?</TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:archer%40nevrax.com"> + <LINK REL="Previous" HREF="000216.html"> + <LINK REL="Next" HREF="000232.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Nel] Dynamic load balancing?</H1> + <B>Vincent Archer</B> + <A HREF="mailto:archer%40nevrax.com" + TITLE="[Nel] Dynamic load balancing?">archer@nevrax.com</A><BR> + <I>Tue, 20 Feb 2001 14:35:01 +0100</I> + <P><UL> + <LI> Previous message: <A HREF="000216.html">[Nel] Dynamic load balancing?</A></li> + <LI> Next message: <A HREF="000232.html">[Nel] Dynamic load balancing?</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#231">[ date ]</a> + <a href="thread.html#231">[ thread ]</a> + <a href="subject.html#231">[ subject ]</a> + <a href="author.html#231">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>According to Nahuel Greco: +><i> You will use standard CORBA?, wich orb? +</I> +Not CORBA. As I said, 'a kind of ORB approach'. Not a straight lift +from existing solutions, who are nice from a development point of view, +but whose features are too generic and too heavy for optimisation. + +><i> What are the "functional" parts that you will be planning? +</I> +I don't have the exact split, which is deeply tied into game design, +but you'll have chiefly: +- access services (who translate between client protocol and service + requests) +- PC manager services +- combat services +- item services +- databaser service (only one) +- pathfinding services +- bots service (AI) +- magic services (maybe, I'm not 100% sure if these aren't managed by the + other services as exceptions to their rules) + +then some geographic-based services + +- ecology managers +- state tracking (the true geography service. That one knows where mobs, + ground items, and PC are relative to each other... but that's about + all it does) + +and a few others, I think, who are related to higher-level game dynamics. + +I might be off, there's still questions on which service handle which +agent for some cases. + +><i> How do you plan to send the map to the user, i mean, if you divide the game +</I>><i> in areas, you can say the client to download the map for an area before +</I>><i> enter, but if you dont use the area-divided approach, then, you must send +</I>><i> the sorrounding terraing at each step that the client do? +</I> +We use a 'mainly static terrain' approach. I.E. the client already has the +various maps parts on-line. We only send gross modifications (i.e. replace +this map part with that pre-patched one, so the rope bridge across the chasm +is no longer there) and local items information (some trees have grown +while you were away). + +Sending the map on the fly requires substantial sacrifices in term of map +complexity (see Asheron's Call for a good example for this). + +><i> There is no risks of overloading the internal network / get out of sync? +</I> +The functional approach is made by looking at the communication between +agents, and putting all agents that discuss with each other the most in +the same services, to avoid network load. Note that agents do *not* +migrate across the network, ever (i.e. a PC full state is always managed +by a specific PC service, regardless of what the PC does or where he +moves). + +-- +Vincent Archer Email: <A HREF="mailto:archer@nevrax.com">archer@nevrax.com</A> + +Nevrax France. Off on the yellow brick road we go! + +</pre> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI> Previous message: <A HREF="000216.html">[Nel] Dynamic load balancing?</A></li> + <LI> Next message: <A HREF="000232.html">[Nel] Dynamic load balancing?</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#231">[ date ]</a> + <a href="thread.html#231">[ thread ]</a> + <a href="subject.html#231">[ subject ]</a> + <a href="author.html#231">[ author ]</a> + </LI> + </UL> +</body></html> |