| Commit message (Collapse) | Author | Age | |
|---|---|---|---|
| * | fix includes for core | Garrett D'Amore | 2025-10-11 |
| | | |||
| * | tests: void instead of empty parameter list | Garrett D'Amore | 2024-12-01 |
| | | |||
| * | init test coverage improvements | Garrett D'Amore | 2024-11-11 |
| | | |||
| * | refactor initialization/finalization | Garrett D'Amore | 2024-11-11 |
| | | | | | | | | | | Applications must now call nng_init(), but they can supply a set of parameters optionally. The code is now safe for multiple libraries to do this concurrently, meaning nng_fini no longer can race against another instance starting up. The nni_init checks on all public APIs are removed now. | ||
| * | fixes #1572 nng creates too many threads | Garrett D'Amore | 2024-01-01 |
| This further limits some of the thread counts, but principally it offers a new runtime facility, nng_init_set_parameter(), which can be used to set certain runtime parameters on the number of threads, provided it is called before the rest of application start up. This facility is quite intentionally "undocumented", at least for now, as we want to limit our commitment to it. Still this should be helpful for applications that need to reduce the number of threads that are created. | |||
