[Crossfire-wiki] [Crossfire DokuWiki] page changed: dev_todo:thread_the_server

[no-reply_wiki at metalforge.org]

A page in your DokuWiki was added or changed. Here are the details:

Date        : 2010/09/04 04:10
User        : ryo
Edit Summary: a few ideas

@@ -23,4 +23,27 @@
  ===== More information =====
  
  FIXME put information from the logs of IRC discussion here
  
+ ===== Nicolas's ideas =====
+ 
+ Things to solve:
+   * thread-safety for shared strings ; not too bad
+   * thread-safety for freed objects, and active objects
+     * solution 1: put'em between mutexes
+     * solution 2: each map has its own list ; issue with linked maps, merge the lists?
+ 
+ 
+ Things that should definitely be threaded:
+   * map loading
+     * caveat: players entering a map will be in a "vacuum" during load ; doesn't seem bad
+   * map saving
+     * caveat: issue with DM command "reset", will need to ensure map is correctly saved
+ 
+ 
+ Things that would be nice to thread:
+   * one thread per map
+     * issue: how will the "Object.Teleport" Python function work, since it couldn't cross thread boundaries? simply remove it, and force script makers to use other means?
+     * same issue with ready_map() through scripts - what happens if the map is already loaded and has its thread running?
+   * thread for socket processing, one per player maybe
+   * ideally, one could thread potentially long operations like massive item selling, or massive item drop
+   * thread socket sending to players, to make the previous operations faster?


IP-Address  : 82.236.87.204
Old Revision: http://wiki.metalforge.net/doku.php/dev_todo:thread_the_server?rev=1160410641
New Revision: http://wiki.metalforge.net/doku.php/dev_todo:thread_the_server

-- 
This mail was generated by DokuWiki at
http://wiki.metalforge.net/