Hi, I do not really know how this process works, who has the final word on which of the proposed ways to do this, we go for?
I like Serge's "attempts" version best, but in this case are maxRetries then to be disregarded? Or is it to be used on the last delaytime entry, if the attempts attribute is missing? (assuming that attempts defaults to 1 if not specified) As this last version is the most versatile, I believe this is the route to go. I would like to start on this monday, so ... --Søren On Thursday 02 October 2003 19:38, Serge Knystautas wrote: > Soeren Hilmer wrote: > > I have been thinking about extending RemoteDelivery to take a list of > > delaytimes. > > > > Something like: > > <delayTime> 600 </delayTime> > > <delayTime> 1600000 </delayTime> > > <delayTime> 21600000 </delayTime> > > <delayTime> 21600000 </delayTime> > > I like this, but would suggest an attribute named "attempts" to each > element. For example, <delayTime attempts="3"> 600 </delayTime> would > try 3 times at 600ms delays before moving to the next delayTime element. -- Søren Hilmer, M.Sc. R&D manager Phone: +45 70 27 64 00 TietoEnator IT+ A/S Fax: +45 70 27 64 40 Ved Lunden 12 Direct: +45 87 46 64 57 DK-8230 Åbyhøj Email: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
