Feature #2574
closed
Explicit usage of time abstractions in public API
Added by Alex Afanasyev about 9 years ago.
Updated about 9 years ago.
Description
Public API should not use method names such as "setInterestLiftimeMilliseconds". Instead, time duration should be captured by the supplied argument type
- Tracker changed from Bug to Feature
This is not a jNDN specific issue. Moved to NDN-CCL.
- Project changed from jndn to NDN-CCL
- Status changed from New to Closed
This approach is taken in NDN-CCL for clarity in typeless languages. (Re-open with design motivation and solution that works for typeless languages if there is one.)
I disagree with closing of the issues that are open ended and may need to be discussed later. Closing them basically means that they will never be worked over.
To mark issues that are undecided, you can use "category" parameter. The issue is still open and I disagree with motivation for closing / approach in CCL.
I created issue specifically for jNDN and java is not a typeless language.
However, the whole issue here is not even about types. It is about not exposing time units in API. It is about explicitly using time units. In most languages one can already use "second(...), millisecond(...), ..." to indicate time explicitly.
Also available in: Atom
PDF
Updated by 
Updated by