[go: up one dir, main page]

Menu

[eeaf89]: / TODO  Maximize  Restore  History

Download this file

36 lines (24 with data), 1.4 kB

Road map:

Release 1.0.0:
- change project status from beta to stable
- update TestLog file
- update site
- upload html API docs

remove config property resource_wait; remove from man page too; update wiki site using --resource-timeout instead of --wait

implement a loop for connect/bind if bind returns an error: this shuold help
to reduce the race condition between a closing daemon and a starting client.
See this thread: https://github.com/tiian/flom/issues/3

IPv6

SSL 

Java (client)

transactional sequences (no holes sequences): use a regex like expression
to describe the sequence; for example:
[0-9](2)[A-Z](3)
produces: 00AAA 00AAB 00AAC ... 01AAA 01AAB ... 01ABA 01ABB 01ABC ...

unique timestamps (no two equal timestamps supplied): use a date like expression
to describe the sequence; for example:
%I%M%S
produces: 213105 213106 213209 ... but not: 213105 213105 even if two clients
ask for a unique timestamp during the same second (the second client will wait)

put inside function flom_accept_loop_chklockers a check if the thread associated to the locker is really active; it the thread leaved (due to an error), make a clean-up phase. This avoid a daemon crash after a thread terminated with an error, but listener thread has a "locker object" already active

implement FIFO, LIFO, FIRST FIT (for numerical resources) lock allocation policies