Re: [RFC] changing sms.validity/sms.deferred to unix timestamp

Hi,

does it mean that it would be up to the user's application in order to
submit _valid_ timestamp? so I wish to make message validity 2 days long,
everytime I have to calculate "future" timestamp, ie. localtime() +
2*24*60. shouldn't it be done somehow automatically?

regards,
Dziugas Baltrunas

On Tue, 1 Apr 2003, Alexander Malysh wrote:

> Hi list,
>
> i would be like to ask, why are validity and deferred in kannel in minutes
> instead of e.g. unix timestamp. I can see that all driver convert this to
> unix timestamp like this: gw_localtime(...) + validity*60...
>
> Second point is that if message can't be send immediately (e.g. Link was
> offline) then our validity and deferred values are not correct, because we
> allways increase our localtime with validity/deferred value.
>
> I believe, deferred/validity values must be absolut instead of relativ to
> sendtime...
>
> Should we change validity and deferred values to unix timestamps to avoid
> unnecessary converting and wrong values?
>
> Comments please ...
>
> --
> Best Regards / Mit besten Grüßen aus Köln
>
> Dipl.-Ing.
> Alexander Malysh
> ___________________________________
>
> Centrium GmbH
> Ehrenstrasse 2
> 50672 Köln
>
> Fon: +49 (0221) 277 49 240
> Fax: +49 (0221) 277 49 109
>
> email: [email protected]
> web: http://www.centrium.de
> msn: [email protected]
>