incubator-openmeetings-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Maxim Solodovnik <>
Subject Re: [DISCUSS] System architecture for Red5 client session store
Date Mon, 03 Dec 2012 17:27:39 GMT
Maybe HashMapStore should be hidden somehow? Make it inner class with
private/package access?

On Mon, Dec 3, 2012 at 1:37 PM, <
> wrote:

> I have not yet finished my refactoring of the session store, but at least
> the existing functionality is now implemented.
> I would like to share some thoughts about the session store.
> All implementations are done against an interfaces, so for example the
> IClientList interface defines the methods needed to save, access or delete
> a session.
> But the "" class is no interface. It is not even a Spring
> Bean. It is bundled with the "" class.
> It will exist only one (static) instance of the HashMapStore.
> The HashMapStore is actually a Map, but a Map with multiple keys.
> Methods of the "HashMapStore" can (and should not) accessed by any class
> other then the ClientListHashMapStore.
> An exception is just the JUnit test that does some result verification by
> accessing the Map directly.
> A possible EHCache implementation could be implemented against the
> IClientList interface.
> However I have not yet done any research on what methods EHCache provides
> to store a multi-key Map (Or if we will end up with a similar approach
> using multiple lists).
> The ISharedSessionStore is different from the IClientList, in that sense as
> it only contains methods that are interesting for the cluster mechanism.
> Sebastian
> --
> Sebastian Wagner

Maxim aka solomax

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message