Hi Torben.
On 10.04.02 (15:05), Torben Nehmer wrote:
> In reality this brings a big administrative overhead: Each
> SnippetDir used globally has to have the same GUID. Pratically
> this is at least difficult to enforce that everyone works with
> the same structure.
Impossible, I'd say. As you write, we need another solution.
> I'm not sure what to do here. It seems to me that we'd need a
> customized Packaging system for MidCOM Packages which does not
> rely on repligard to move MidCOMS around. Multiple discussions
> seem interesting here:
>
> 1. Filebased Storage for distribution
Don't understand this -- do you mean tar-packaged directory trees
as proposed by Armand for his serialize/bootstrap tools?
> 2. APT Like packaging, working entierely without repligard
> 3. Using repligard with an wrapper script that can correctly
> handle MidCOM Elements by name, and not by GUID.
>
> Personally I'd prefer (2), because it will give the most
> flexibility...
I'd vote for (3), because it's the easiest way to go. We could
let repligard handle the XML writing & parsing stuff as well as
building the right trees, deciding what to import/export etc.
and could adjust GUIDs accordingly to the respective target
database. If I'm not overlooking anything right now, we could
even implement MidCOM replication via (3) with YAMP, couldn't
we? (Using a script hook to replace MidCOM "domain" GUIDs.)
phr
--
Linksystem Muenchen GmbH [EMAIL PROTECTED]
Schloerstrasse 10 http://www.link-m.de
80634 Muenchen Tel. 089 / 890 518-0
We make the Net work. Fax 089 / 890 518-77
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
