ObjFW  History of src/OFKernelEventObserver_LockedQueue.h of e9b4700cb6b71e6b

History of the file that is called src/OFKernelEventObserver_LockedQueue.h at check-in e9b4700cb6b71e6b

2016-03-20
14:07
Deleted: Use the locked queue for kqueue and epoll as well

_readObjects must only be changed from the thread running the observer
and not from a thread adding or removing objects to observe. This is
already handled by the locked queue used by poll and select, so the best
way to solve this is to use the locked queue for kqueue and epoll as
well. check-in: [45518ae7b7] user: js, branch: trunk, size: 0

2016-01-03
00:41
Update copyright

While at it, also update the mail address. file: [67a5a5872e] check-in: [2a27cf3000] user: js, branch: trunk, size: 1193 [annotate] [blame] [check-ins using] [diff]

00:35
Fix a regression from the previous refactorization

kqueue and epoll were not updating _readObjects and _writeObjects
anymore, since this was done by the queue handling code, which they no
longer use after the refactorization. file: [e5e6d24907] check-in: [258b8a4944] user: js, branch: trunk, size: 1189 [annotate] [blame] [check-ins using] [diff]

2015-12-29
21:33
Added: Refactor OFKernelEventObserver

This moves the locked queue for actions to
OFKernelEventObserver_LockedQueue, which is now used for select and
poll, but skipped for kqueue and epoll, as they natively support changes
from another thread.

This fixes the problem that removing an object is delayed until the next
observe call - at which point it might have already been closed, meaning
the fd is no longer available. This was mainly a problem with kqueue, as
closing the fd already removed it from the kqueue, which then resulted
in an error being returned when trying to manually remove the fd from
the kqueue. file: [e60316af1b] check-in: [e9b4700cb6] user: js, branch: trunk, size: 1283 [annotate] [blame] [check-ins using]

Fossil 2.23 [47362306a7] 2023-11-01 18:56:47
This page was generated in about 0.024s