Petr Škoda d79d5ac276 MDL-31501 rework user session architecture
List of changes:
 * New OOP API using PHP namespace \core\session\.
 * All handlers now update the sessions table consistently.
 * Experimental DB session support in Oracle.
 * Full support for session file handler (filesystem locking required).
 * New option for alternative session directory.
 * Official memcached session handler support.
 * Workaround for memcached version with non-functional gc.
 * Improved security - forced session id regeneration.
 * Improved compatibility with recent PHP releases.
 * Fixed borked CSS during install in debug mode.
 * Switched to file based sessions in new installs.
 * DB session setting disappears if DB does not support sessions.
 * DB session setting disappears if session handler specified in config.php.
 * Fast purging of sessions used in request only.
 * No legacy distinction -  file, database and memcached support the same functionality.
 * Session handler name included in performance info.
 * Fixed user_loggedin and user_loggedout event triggering.
 * Other minor bugfixing and improvements.
 * Fixed database session segfault if MUC disposed before $DB.

Limitations:
 * Session access time is now updated right after session start.
 * Support for $CFG->sessionlockloggedinonly was removed.
 * First request does not update userid in sessions table.
 * The timeouts may break badly if server hosting forces PHP.ini session settings.
 * The session GC is a lot slower, we do not rely on external session timeouts.
 * There cannot be any hooks triggered at the session write time.
 * File and memcached handlers do not support session lock acquire timeouts.
 * Some low level PHP session functions can not be used directly in Moodle code.
2013-09-21 13:11:56 +02:00
..
2013-05-20 15:33:19 +02:00
2011-03-01 12:26:49 +01:00
2013-09-10 13:02:35 +12:00

Official Chat Module for Moodle
------------------------------

The chat module now supports a backend daemon for
more efficiency.

It's still buggy and being worked on, but if you
want to test it and help out here are some quick
instructions:

1) Admin -> Config -> Modules -> Chat -> Settings

2) Set the method to "sockets" and set up the ports etc

3) Start the server like this (from the Unix command line):

   cd moodle/mod/chat
   php chatd.php --start &

4) Go to a chat room in Moodle and open it as normal.

------

KNOWN PROBLEMS

 - User list is not always working
 - Some browsers (eg Safari) cause lines to be repeated
   by 10 - 20 times
 - Occasionally "Document was empty" messages

Help solving these very welcome!


Martin, 31 July 2004