Hi Micha,
Ok, it is really complex. so I try a rudimentary example of the internal logic.
2. export data to child 2.1. export config (e.g. dataexchange.xml) 2.2. check which objects of which datatype must be exported to the child 2.3. export these objects 2.4. write logs of this 2.5. export my import logs from this childI hope this gives an overview about the logic inside. I don't like more details because the details are to implementation specific for a design discussion. Point 2.2 is the most performance critical one.
Hmm, I dont see a real performance problem here when we put some indexes on the database and use well-balanced querys, I am aggainst a second table because it will be prone to inconsitency or we have to spend some additional sync flag......
Oliver -- Diese Nachricht wurde digital unterschrieben oliwel's public key: http://www.oliwel.de/oliwel.crt Basiszertifikat: http://www.ldv.ei.tum.de/page72
smime.p7s
Description: S/MIME Cryptographic Signature
