[
https://issues.apache.org/jira/browse/RNG-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15523492#comment-15523492
]
Gilles commented on RNG-19:
---------------------------
bq. This is unlikely, the scope of random number generators is much more
limited than the whole field of math algorithms.
I was referring to the tendency of extending the scope (which I readily agree
that it was quite easy with CM).
I don't deny that it looks like it could be a useful feature to have, just not
in the same namespace as "implementations of PRNG algorithms".
bq. What kind of problems?
* Dealing with OS files (the management it entails cannot be performed through
the intended API)
* Save/restore (what is the state of "/dev/random"?)
* Portability (or more exactly _non-portability_)
I really do not want to engage in the path that leads to support the wrapping
of any source of randomness (as opposed to just providing the "lowest-level"
algorithms and let higher-level libraries do the wrapping to their taste).
>From CM experience, I advocate that we stick to the most focused scope for
>release 1.0, and that extensions are implemented in another repository (a.k.a
>"Commons RNG Utils").
> System generator (/dev/random)
> ------------------------------
>
> Key: RNG-19
> URL: https://issues.apache.org/jira/browse/RNG-19
> Project: Commons RNG
> Issue Type: Wish
> Reporter: Emmanuel Bourg
> Priority: Minor
>
> Commons RNG could include a random number generator based on the output of
> /dev/random or /dev/urandom on Unix systems.
> Commons Crypto has an implementation that could be used as a starting point:
> https://github.com/apache/commons-crypto/blob/master/src/main/java/org/apache/commons/crypto/random/OsCryptoRandom.java
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
