Opened 11 years ago
Closed 6 years ago
#6339 closed Feature Requests (wontfix)
timed_lock functionality should also take a time duration
| Reported by: | Owned by: | Ion Gaztañaga | |
|---|---|---|---|
| Milestone: | To Be Determined | Component: | interprocess |
| Version: | Boost 1.48.0 | Severity: | Optimization |
| Keywords: | timed_lock | Cc: |
Description
Interprocess use of locking functionality for scoped_lock expresses a timed_lock in terms of an absolute boost::posix_time::ptime time. It should also support a time duration from the current time when the scoped_lock is constructed. It can use the boost::posix_time::time_duration class for this.
For compatibility with C++11 it should also use boost::chrono, both for an absolute time and for a time duration.
Change History (2)
comment:1 by , 9 years ago
comment:2 by , 6 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
Closing the bug as users have not shown interest in this feature. Interprocess follows POSIX's convention here using absolute timeouts.
Note:
See TracTickets
for help on using tickets.
The same applies for interprocess_condition