trxx

Multiprocessing, because on a larger scale one machine just won't be able to cope with the load. It'd be very interesting how much overhead there is when you run all seperated processes communicating via CORBA on one machine compared to doing it multithreaded. Splitted processes will naturally lead to good design, whereas multithreading is imo more likely to be implemented in a sloppy way that will lead to unsolvable race conditions. But let's put things clear: multithreading has limits, multiprocessing does not. The question is where those limits are. How many clients are atm supported by mangos? How many will it be with line of sight checking? I just don't know whether one machine is enough. I don't see it like wyk3d. I think making mangos multithreaded is the pragmatic "we want some performance in some way"-way wheras multiprocessing is the theoreticaly perfect and scalable solution if done right and IPC doesn't generate an overhead as high as the power improvements of (affordable) clustering gives us. This is of course mostly dependent on the speed and mem usage CORBA has when the processes run on a single machine.

*BUMP* Why doesn't a dev remove the table? I think it should be updated or removed, because in the current state it only scares away potential users. Edit: The best solution might simply be flagging it out-of-date!

Hi I think working talents/spells are most important for gaming, so I had a look at the working spells table in trac: http://www.mangosproject.org/trac/wiki/spells ...and began testing. So i found out that Warrior: Overpower, Warrior: Booming Voice, Mage: Improved Aracane Missiles work (Only highest ranks tested). Is this table up-tp-date? The warrior page was updated in december, so you could get the idea. Perhaps we should make a new table (in a wiki open to public?) or update this one as working spells are crucial for the game. What do you think?