Quiting http://vibed.org/api/vibe.http.session/MemorySessionStore
If the server is running as a single instance (no thread or process clustering), this kind of session store provies the fastest and simplest way to store sessions. In any other case, a persistent session store based on a database is necessary.
Is my understanding correct - HTTP server does not do any locking when interacting with MemorySessionStore and basically the only way to get it with a multiple worker threads is to make similar implementation with mutex securing every method call? What is the general policy in vibe.d server code for global mutable entities?