I think having these kinds of things configurable is just going to cause issues in the long run, it's an API (even if this is the websocket part), you wouldn't go and ask github or twitter to be able to configure what format their date formats come back in would you? unix timestamps can cause a lot of issues when it comes to JS/PHP etc - not so much I guess when it comes to a call thats going on for 2 minutes but.... I'd rather keep to a single format and for that format to be one that can be parsed easily - so YYYY-MM-DD HH:MM:SS, it's a big topic and unfortunately there was never an agreed standard :( http://stackoverflow.com/questions/10286204/the-right-json-date-format Dan On Wed, Oct 16, 2013 at 12:43 AM, Alistair Cunningham < acunningham at integrics.com> wrote: > Is there any chance we could have an option to use Unix timestamp format > (seconds since 1970-01-01 00:00:00 ignoring leap seconds) in the ARI events > (e.g. creationtime) and (if there are any) the actions? > > I suspect (correct me if I'm wrong) that Asterisk uses Unix format > internally, so for apps that do so too this would save some formatting and > parsing on each end. > > I'd be perfectly happy to have this a setting in ari.conf that's disabled > by default. > > -- > Alistair Cunningham > +1 888 468 3111 > +44 20 799 39 799 > http://integrics.com/ > > ______________________________**_________________ > asterisk-app-dev mailing list > asterisk-app-dev at lists.digium.**com <asterisk-app-dev at lists.digium.com> > http://lists.digium.com/cgi-**bin/mailman/listinfo/asterisk-**app-dev<http://lists.digium.com/cgi-bin/mailman/listinfo/asterisk-app-dev> > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-app-dev/attachments/20131016/a91a57e9/attachment.html>
