Re: Re: [Tm4j-tmnav-dev] StoreManager Implementation

[Kal A. <ka...@te...>]

On Sun, 2003-08-31 at 23:01, Martin Stockhammer wrote:
> Yes that's true. I saw this. I would like to put all the tm4j-dependencies into the
> panckouckeStore and make the StoreManagerImpl only dependent on the panckoucke
> api.
> I think the store implementation are very dependent on the backend that is used. 
> So I thought to create a store implementation for each individual backend and let
> the StoreManager choose the right store-Implementation for it's task, dependent
> on the current context.
> For example it might be possible, that a client has its local store for some topic
> maps and wants to use the webservice for other topicmaps.
> 
> But on the first view I see some problems if we uses store implementations parallel.
> The Locator-Adresses must be unique for each store implementation. Merging of
> topicmaps over different stores is very likely not possible (any ideas?).
> 

Take a look at the org.tm4j.topicmap.unified package. Its a kind of
read-only, dynamic merging of topic maps which should work across
different stores. It doesn't do name-based merging, but it does do
subject indicator and subject address merging. It would probably be
quite bandwidth-intensive across multiple web services unless you were
able to do some local caching (this is what my P2P application does -
the Unified backend is actually a unified view of the cached data and
the working data and the cache is added to as the user browses around
this unified view).

Cheers,

Kal
-- 
Kal Ahmed, Techquila
Standards-based Information Management
e: ka...@te...
w: www.techquila.com
p: +44 7968 529531