-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for any messages queue, e.g. ZeroMQ / AMQP / RabbitMQ #96
Comments
RabbitMQ java client seems to be the library to use. |
I see that you intent to have this as an implementation platform. This means
via AMQP. What would be the purpose of that and who should be the receiver of those messages in which format? |
AMQP is a protocol specification. There's support in nearly every commonly used programming language, not even java only. No idea what you mean with format. |
The format is only the least important point of the issues mentioned above. Could you please elaborate on the other questions? |
It seems that there is no actual use case behind this request. Closing that issue. |
Lyra is a high-availability RabbitMQ client (for AMQP as the used protocol). |
A clear use case is still missing. I already asked twicve but still did not get any meaningful answer. |
Regarding a use-case, do you have in mind something like: It should be
possible to send information to jvxml's FIA, without the jvxml app
requesting it, so that grammars and prompts might be interrupted and the
app directed to another form or doc location?
…On Sun, 17 Nov 2019, 6:09 am Raphael Groner, ***@***.***> wrote:
Lyra is a high-availability RabbitMQ client (for AMQP as the used
protocol).
https://github.com/jhalterman/lyra
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#96?email_source=notifications&email_token=AA5RKQ3AEBHCFE2YRMY6TRLQUFGBJA5CNFSM4IT3AIUKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEIM3PQ#issuecomment-554749374>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA5RKQ43OSKLSJKRL4DHYELQUFGBJANCNFSM4IT3AIUA>
.
|
There are currently 3 protocols available in JVoiceXML to interact in MMI
What would be the benefit of supporting a 4th protocol? |
Where can one read more about how to use these protocols with jvxml?
…On Tue, 19 Nov 2019, 11:22 pm Dirk Schnelle-Walka, ***@***.***> wrote:
There are currently 3 protocols available in JVoiceXML to interact in MMI
- HTTP
- uMundo (an abstraction over ZweroMQ)
- Sockets
What would be the benefit of supporting a 4th protocol?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#96?email_source=notifications&email_token=AA5RKQ2QN6T6BJPXHZQG7BDQUTQT3A5CNFSM4IT3AIUKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEQ7L3Q#issuecomment-555873774>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA5RKQ4GKPFPPSZFEYTXXSLQUTQT3ANCNFSM4IT3AIUA>
.
|
These are implemented as CallManagers and can currently not be used within telephony environments. See the corresponding call managers for a reference
Unfortunately, there is no other documentation available |
In case there's a typo and you mean ZeroMQ instead, then you can consider my request as obsolete. ZeroMQ is similiar to AMQP. |
Well, as somewhere else stated I've somehow possible experiments with more complexity in mind. |
A long outstanding request. Would it be possible to have native support for AMQP with (any new) one of an implementation? I tried to start something but never managed to get response from core development. My work did not get even further and I plan to discontinue at all because of really lack of time but I still want to let you all know.
https://gitlab.com/voice-mediator/jvxml-amqp
See especially in this paper:
https://academiccommons.columbia.edu/download/fedora_content/download/ac:165655/content/Virtualization.pdf
The text was updated successfully, but these errors were encountered: