Recent changes to bugs

#4 failure build for Windows

2015-08-06T12:19:39.091000Z

According to the ChangeLog, the MinGW support has been dropped.

Too bad! JsonRpc-Cpp used in our cross-platform project for Linux, OS X and Windows.

However the code compile fine with Microsoft Visual Studio 2015.

No way. MSVC is a proprietary compiler, so we always give preference to GCC.

#4 failure build for Windows

2015-08-04T10:54:14.740000Z

It appears that MinGW does not have suport for poll() function.

According to the ChangeLog, the MinGW support has been dropped. However the code compile fine with Microsoft Visual Studio 2015.

Anyway if you want to contribute a patch to support MinGW, I will happy to review it.

failure build for Windows

2015-08-03T22:25:44.646000Z

Failure build for Windows on MXE (http://mxe.cc/).

#3 tcp-server accepting logic non thread-safe in same applications

2015-08-02T09:52:37.734000Z

status: accepted --> closed-fixed

#3 tcp-server accepting logic non thread-safe in same applications

2015-07-26T16:51:33.422000Z

status: open --> accepted
assigned_to: Sebastien Vincent
Priority: 5 --> 3

#3 tcp-server accepting logic non thread-safe in same applications

2015-07-26T16:51:16.777000Z

Thank you for the report.

Yes select() has some limitations, so change to poll() is a good idea.

In your patch, it misses the poll() for the TCP client socket descriptor. But anyway I will definitely replace the select() stuff by poll().

tcp-server accepting logic non thread-safe in same applications

2014-06-14T18:20:49.369000Z

In my client-server application I use libevent for a heavily accepting and manipulating with client connections (video streaming application). In your library you are using select() with precalculated max_sock identifier for non-blocking accept new connection, and in some time it can happens situation, when a system generated sock identifier in other program threads can match with your max_sock and then program state will be non consistent. In my patch I replace select() logic to poll() logic without using self generated sock identifier and problem has gone.

tcp-server accepting logic non thread-safe in same applications

2014-06-14T18:20:49.369000Z

Ticket 3 has been modified: tcp-server accepting logic non thread-safe in same applications
Edited By: Sebastien Vincent (s-vincent)
Status updated: u'open' => u'accepted'
_priority updated: u'5' => u'3'
Owner updated: None => u's-vincent'

tcp-server accepting logic non thread-safe in same applications

2014-06-14T18:20:49.369000Z

Ticket 3 has been modified: tcp-server accepting logic non thread-safe in same applications
Edited By: Sebastien Vincent (s-vincent)
Status updated: u'accepted' => u'closed-fixed'

#2 ms in waitmessage in server is truncated

2013-02-07T16:44:38.591000Z

status: open --> closed-fixed
milestone: -->