Hi!
First, of all, how many and large files are we talking about? It would be rather expensive to loop through them in flow, open them each by each, looking for the element <expiry-date/>, and if it is found, delete the file.
Well, the number is not predictable, but it would be rather a few than a lot (<10).
But, if you look every day, then files that are not modified within the last 24 hours won't have to be checked again. Therefor, you could use the directory generator.
Well, the files aren't going to be modified ever. They are messages to users, that expire after a certain date. Each message is contained in one file and these files are then aggregated into one message file that is presented to the user. When a message has expired it is supposed to be deleted so that in the next aggregation run it won't re-appear.
Maybe this is not the easiest way to do it. I thought about putting all messages into one file from the beginning and then have them searched for expired ones when the file is called for display, but I thought the other approach was better.
christian --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
