Ives Steglich wrote:
a quite simple possible solution could use a timestemp instead of the serial numbers, like now
so another mail *g*, i just finished a solution which will use the timestamp-approach (and its working), but there is still a little issue to be solved with this:
if one does import form a higher level again, before exporting again and updating at the higher level (or at least with an old exchange-data-file), the mail-msg gets overwritten (even if they are already present) and therefore a new timestamp so they will get send again, but maybe this should be an expected behavior?
(this won't happen with the serial aproach, but only if we remember which serials have been used alread, the simple counter approach breaks as the point, when we leave out serials, like seen and shown)
so - what to do now? ,o)
we can stop overwriting already present files for example, which would
be the cleaner approach, since if i let it overwrite (which is like an update so) it should therefore get send again... shouldn't it?
but for the momment i don't put the patch into cvs, before i don't get some response
File::stat must be used for it, but i think, this is a standard perl package? otherwise we have to check for it, at the install and configure stuff of course...
greetings dalini
--
Ives Steglich Email: [EMAIL PROTECTED]
System Administration Tel.: +49 (0)3677 - 69 4382/4383
Fax: +49 (0)3677 - 69 4399Fraunhofer Institute for Digital Media Technology Langewiesener Strasse 22 98693 Ilmenau Email (private): [EMAIL PROTECTED] Germany http://www.openca.org
------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click _______________________________________________ OpenCA-Devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/openca-devel
