Unnamed repository; edit this file 'description' to name the repository. https://www.cgit.space/~steering/inspircd++.git/atom/src/socketengines?h=v3.0.0a10 2017-10-22T18:45:05Z 2017-10-22T18:45:05Z Peter Powell 2017-10-22T02:10:48Z urn:sha1:63e300ed082b82530ad5ae0949f45686746b7c9b 2017-10-22T18:44:45Z Peter Powell 2017-10-22T01:27:25Z urn:sha1:b1098712771ab823042fcf8614a706c76c2ff401 2017-10-22T18:42:11Z Peter Powell 2017-10-22T14:10:49Z urn:sha1:d4414f54910aeaa4809a7eacea75a089a0820f40 After discussing this with Adam we have decided that there is very little point in keeping this now that Solaris has been killed. Any legacy Solaris users will have to make do with poll. This change does not affect users of Solaris forks like Illumos as they have support for epoll which will have already been selected over Solaris IOCP by configure. 2017-10-22T00:27:10Z Adam 2017-10-22T00:27:10Z urn:sha1:7b2a78aa10e037d8d4b56914bc43651f552c0cb3 2017-07-12T13:25:28Z Peter Powell 2017-07-12T13:25:28Z urn:sha1:f471083cd0519d47c7c7a09029813ede41994f7b Merge v2.0.23 and v2.0.24 into master. 2017-07-11T12:22:02Z Robin Burchell 2017-03-22T16:59:08Z urn:sha1:8e8b0719bf58e2d875c06698f86377189da87e16 The write counters were close to useless because they were only incremented on a write "event" which is only triggered when writing would block. Read handling was a little more useful in that all reads must happen through the socket engine, so these were happening at the correct time, but we can clean this up by doing it in the SE itself rather than each platform port. This means that both read and write events are now easily and usefully defined as "a syscall of either read or write was attempted". We also count empty read and write events as being an event, because they still were an attempt to poll a socket in some way. This may help to identify "bad" code which is repeatedly trying to read a socket for some reason. Lastly, we check for failed read/write calls, and log them as an error event. A lot of the time, this is how sockets are determined as being disconnected (ie. at read/write time). While we're at it, split Update() in two to make the calls more self-describing. This has no real impact since only one call is made at a time anyway. 2017-07-09T21:45:00Z Peter Powell 2017-07-09T21:36:40Z urn:sha1:c0aba5b728b0a921d95ec120aa638dab1520b42f 2016-11-22T13:49:43Z Adam 2016-11-22T01:56:39Z urn:sha1:7ddef68f44ecb01f891e55a680078f7857fb866f 2016-08-19T15:10:00Z Peter Powell 2016-08-19T12:59:07Z urn:sha1:047e30a4179acb6cfe926c5f6fc4e447addd69ed 2016-08-19T15:10:00Z Peter Powell 2016-08-19T11:56:01Z urn:sha1:a7ca68ff7249da865b5b572b6430cf2e5d34b7c3