Setting up a repository

[Keith Hodges]

Norbert Hartl wrote:
> On Thu, 2008-04-17 at 17:54 +0100, Keith Hodges wrote:
>   
>> Norbert Hartl wrote:
>>     
>>>>> 4. Is acceptable/possible to have more than 1 repository to 1 system ?
>>>>>       
>>>>>           
>>>> Yes, not only is it acceptable, it is recommended to partition your
>>>> domain by meaningful boundaries.  For example, in my system I separate
>>>> the Accounting domain from the Contacts; each in their own repository,
>>>> even though Accounts reference Contacts residing in the other
>>>> repository.  This is accomplished via MagmaForwardingProxy.
>>>>
>>>> This partitioning provides many benefits.
>>>>
>>>>     
>>>>         
>>> That sounds very good. How does the forwarding proxy know where to reach
>>> the object? Does the proxy know some repository id and that will work as
>>> long as I have a session open pointing to the corresponding repository?
>>>
>>> thanks,
>>>
>>> Norbert
>>>   
>>>       
>> The "Magma seasideHelper" framework has code for this partitioning. You 
>> define a root object for each partition or domain, and then use
>> aMagmaSessionHelper rootAs: TheDomainRootClass to return the appropriate 
>> root object... well at least that is the theory. I havent had as much 
>> chance as I would like to test this out fully.
>>
>>     
> So, this will also work on an arbitary number of magma databases on 
> several hosts? 
>
> Norbert
>
>   
Actually, I didnt read fully what Chris was proposing. I think we need 
some documentation on the ForwardingProxy since I myself have no idea 
how to acomplish what he is proposing. I think that he is suggesting 
that we place data from different domains in separate databases.

My scheme is for placing data from different domains into a single 
database. Each domain root class knows where it is stored in relation to 
the overall database, so that the client doesnt have to know the 
details. The theory being to allow modules to be published that can be 
combined, without any need for configuration. E.g. a users accounts, 
logging in and management module for seaside could be combined with a 
webshop module, or a blogging module.

Keith