|
From: Lars H. <he...@se...> - 2008-10-21 16:34:45
|
[...]
> The topic map and the system could also be writable but there wouldn't
> be any synchronisation with the TMShare server (at least not in the
> initial version).
[...]
Basically, tinyTiM would act as client which consumes the topic maps
provided by the TMShare server. After the TopicMapSystem has been
initialized, the system would contact the TMShare server and load the
latest snapshots from the server (could be done lazily, i.e. the
initial request would just download the information about the provided
topic maps).
After a topic map has been read, tinyTiM would act independent of the
TMShare server (it does not report changes to the server, for
example).
The system could go into a another tinyTiM subproject, the core engine
wouldn't be effected. The TopicMapSystemFactory would look if the
feature "TMShare" is set and then load the specialised TopicMapSystem
(i.e. Class.forName("org.tinytim.tmshare.TopicMapSystem");). The user
would have to include additional libs only if she wants to have that
functionality.
The question is, if it would be valuable to implement such a system or
if it would be a waste of time and effort.
Best regards,
Lars
--
Semagia
<http://www.semagia.com>
|