<!-- Kamailio Pull Request Template -->
<!--
IMPORTANT:
- for detailed contributing guidelines, read:
https://github.com/kamailio/kamailio/blob/master/.github/CONTRIBUTING.md
- pull requests must be done to master branch, unless they are backports
of fixes from master branch to a stable branch
- backports to stable branches must be done with 'git cherry-pick -x
...'
- code is contributed under BSD for core and main components (tm, sl, auth, tls)
- code is contributed GPLv2 or a compatible license for the other components
- GPL code is contributed with OpenSSL licensing exception
-->
#### Pre-Submission Checklist
<!-- Go over all points below, and after creating the PR, tick all the checkboxes
that apply -->
<!-- All points should be verified, otherwise, read the CONTRIBUTING guidelines
from above-->
<!-- If you're unsure about any of these, don't hesitate to ask on
sr-dev mailing list -->
- [X] Commit message has the format required by CONTRIBUTING guide
- [X] Commits are split per component (core, individual modules, libs, utils, ...)
- [X] Each component has a single commit (if not, squash them into one commit)
- [X] No commits to README files for modules (changes must be done to docbook files
in `doc/` subfolder, the README file is autogenerated)
#### Type Of Change
- [ ] Small bug fix (non-breaking change which fixes an issue)
- [X] New feature (non-breaking change which adds new functionality)
- [ ] Breaking change (fix or feature that would change existing functionality)
#### Checklist:
<!-- Go over all points below, and after creating the PR, tick the checkboxes that
apply -->
- [ ] PR should be backported to stable branches
- [X] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
<!-- Describe your changes in detail -->
Added a publish function to nats module. When the function is called, the routing process
tries to connect to the url (param) and tries to send the payload (param) to the subject
queue (param). No libuv is used for this.
Probably a better approach is to make publisher workers (like subscriber workers) and pass
payload from routing processes to publisher worker processes via shared memory. Right now
I see this as an improvement and find the new function good enough, for now.
@eschmidbauer what do you think of this?
Thank you,
Stefan
P.S. Will update doc after review.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2915
-- Commit Summary --
* <a
href="https://github.com/kamailio/kamailio/pull/2915/commits/121ae374e…quot;>nats:
Add publish function</a>
-- File Changes --
M src/modules/nats/nats_mod.c (71)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2915.patch
https://github.com/kamailio/kamailio/pull/2915.diff
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/2915