micheleselea

onIdle and onBusy handlers, can be usefull to handle a dead socket, for example a socket that do not send you nothing for X seconds. That was the main reason...

yes @aleks-f you are right, it's onBusy that do the "socket checker" in my project and I already had to extend the SocketReacor

No I didn't because it's some kind of tricky error, because is not happen so frequently, and it's inside the LocalDateTime class, so usually a subsequent call to that function...

It's seems to me some "locked" structure or some kind of concurrent access

@aleks-f exactly windows has a reverse order like that: ``` void LocalDateTime::determineTzd(bool adjust) { if (adjust) { std::time_t epochTime = _dateTime.timestamp().epochTime(); #if defined(_WIN32) || defined(POCO_NO_POSIX_TSF) #if defined(_WIN32_WCE) && _WIN32_WCE <...

the problem is that you could create a new file, clearing existing one, because you get false or you could leave a file that you must delete but you think...

I'm going to dig about it. For what I understand from RFC https://www.ietf.org/rfc/rfc5905.txt it's possible using that 1852 timestamp using a fixed offset of 2,874,597,888 that is something familiar looking...

looking at the RFC I think the way we should initialize _originateTimestamp is using the get_time() below. I did some tests and wireshark decodes good. ``` #define JAN_1970 2208988800UL /*...

Ok but I have the other pull request pending. I cannot fork another project until the other is merged isn't it?

I don't know why but I can't sync with github application the the forked repositories since last week, It tells me that there's a module that can't download