Re: [fpc-pascal] is resourcestring translation thread safe ?

2013-02-21 Thread ik
On Thu, Feb 21, 2013 at 9:07 PM, Sven Barth wrote: > On 21.02.2013 19:14, ik wrote: >> >> On Thu, Feb 21, 2013 at 8:06 PM, Sven Barth >> wrote: >>> >>> On 21.02.2013 17:55, ik wrote: Hello, Let's say I have a multi-threaded cgi (such as brook framework), and I use re

Re: [fpc-pascal] is resourcestring translation thread safe ?

2013-02-21 Thread Sven Barth
On 21.02.2013 19:14, ik wrote: On Thu, Feb 21, 2013 at 8:06 PM, Sven Barth wrote: On 21.02.2013 17:55, ik wrote: Hello, Let's say I have a multi-threaded cgi (such as brook framework), and I use resourcestring to translate strings. Does the translation of resourcestring will be based on a th

Re: [fpc-pascal] is resourcestring translation thread safe ?

2013-02-21 Thread ik
On Thu, Feb 21, 2013 at 8:06 PM, Sven Barth wrote: > On 21.02.2013 17:55, ik wrote: >> >> Hello, >> >> Let's say I have a multi-threaded cgi (such as brook framework), and I >> use resourcestring to translate strings. >> Does the translation of resourcestring will be based on a thread - >> that is

Re: [fpc-pascal] is resourcestring translation thread safe ?

2013-02-21 Thread Sven Barth
On 21.02.2013 17:55, ik wrote: Hello, Let's say I have a multi-threaded cgi (such as brook framework), and I use resourcestring to translate strings. Does the translation of resourcestring will be based on a thread - that is a copy for each thread, or will it be globally changed ? It's globall

[fpc-pascal] is resourcestring translation thread safe ?

2013-02-21 Thread ik
Hello, Let's say I have a multi-threaded cgi (such as brook framework), and I use resourcestring to translate strings. Does the translation of resourcestring will be based on a thread - that is a copy for each thread, or will it be globally changed ? Thanks, Ido __

[fpc-pascal] Re: JSON dates

2013-02-21 Thread Reinier Olislagers
On 21-2-2013 12:18, Graeme Geldenhuys wrote: > On 2013-02-21 09:59, Reinier Olislagers wrote: >> Is this ISO 8601 format currently the most widely used? It seems the >> most sane to me. > > Yes, that is the safest and most understood format. So the JSON date wars have more or less ceased then? Any

Re: [fpc-pascal] JSON dates

2013-02-21 Thread Graeme Geldenhuys
On 2013-02-21 09:59, Reinier Olislagers wrote: > > Noticed that Firefox gives this: > new Date().toJSON(); > /* > 2013-02-21T09:47:42.467Z > */ > which looks like an ISO date to me. Yes, that is the ISO 8601 format, and the only sane format you should use. Even in my database application, my date

[fpc-pascal] JSON dates

2013-02-21 Thread Reinier Olislagers
Hi, Creating a client/server scanning application that uses JSON to exchange data. Noticed there's no support for dates in the JSON specs; apparently various approaches are used (Unix epoch/ISO 8601 date strings/something Microsoft did). Noticed that Firefox gives this: new Date().toJSON(); /* 2