I'm building a Rust API for the Dart Native Extensions API.
I have found out about something called a "Native Instance".
I cannot find anything relating to it, or discussing it on google, or SO.
The functions in question (Rust link (C link)):
Dart_AllocateWithNativeFields (C)
Dart_GetNativeInstanceFieldCount (C)
Dart_GetNativeInstanceField (C)
Dart_SetNativeInstanceField (C)
A few questions:
What would Dart_AllocateWithNativeFields do? IE. What would one use it for?
What would the use of a so called "Native Instance" be like for a Dart user?
What is the native_fields parameter of Dart_AllocateWithNativeFields for/What should I supply it with?
Should I even go about supporting this in an idiomatic Rust API?
What is a "native field"?
What is a "native instance"?
These functions have an unfortunate combination of little and bad documentation.
Related
I'm looking for a way to integrate the Google Assistant into my chatbot and be able to get answers to general questions like "whats the weather?", "how tall is X?", "what does X mean?" etc. (just how Google Home works). Ideally this would be over a REST API and I'd get the response back inside of a JSON payload.
I looked through the Google Assistant SDK docs but it wasn't clear on how I could host/build an API that does this. Any ideas on if something like this already exists?
Yes, you use the Google Assistant SDK.
There isn't a REST API, since other requirements for the SDK are poorly suited for REST. Instead it uses gRPC, which lets them publish a standard interface and lets you compile this interface to local language bindings.
IF you are using Python, C++, or Node.js, there are already libraries available which allow you to skip the gRPC setup yourself.
Im wondering when the engineering team at Twilio expects to release the outbound dialing functionality, which was indicated is being actively worked on here
https://support.twilio.com/hc/en-us/articles/360010789173-How-do-I-Make-Outbound-Calls-with-Twilio-Flex-
I'd imagine a lot of people leveraging twilio flex would like this as its a common case.
I realize that we can add this type of functionality on our own by programming against the apis, and even use the plugin such as
https://github.com/lehel-twilio/plugin-dialpad
My only concern with using the above plugin is that it
May be deprecated if twilio engineers add this natively to flex UI
Since only 1 plugin can be used at a time, if customizations were made to a plugin already (call it plugin B), I would have to merge the plugin code contained in the plugin-dialpad github repo above (call this plugin A) into the code base of Plugin B.
It would be great if twilio supported adding mutiple plugins?
Any feedback twilio team/evangelists on this? Id imagine its a common use case.
The team has kindly responded and said that they are targeting the end of year for releasing this natively into twilio flex
it's already available but experimental
https://www.twilio.com/changelog/outbound-calling-experimental-feature
here is a guide on setup
https://www.twilio.com/docs/flex/dialpad-end-user-guide
there is a confusing part with workflow thing so I'm going to explain in more details:
1) go to https://www.twilio.com/console/taskrouter/workspaces
2) select your workspace
3) go to Workflows
4) click on Assign to Anyone or whatever workflow you want to use for outbound calls
5) Click Add filter
6) If you have other filters it's better to place this one on top because if other filter matches this task it won't work
7) set MATCHING TASKS to flexOutboundDialerTargetWorker != null
8) set EXPRESSION to task.flexOutboundDialerTargetWorker == worker.contact_uri
9) click save
that's it. hope it saves someone time
Flex supports outbound dialing in form of the following two features
Native Dialpad available in Flex UI
Programmability construct viz. startOutboundCall to build use cases like click-to-dial.
starting today.
Check out the blog post.
Disclaimer : I work at Twilio.
DISCLAIMER: This question mentions Google Contact Center AI, which is currently in
alpha. DO NOT PROVIDE any references to CCAI api. The solution soley relies on Twilio Flex code & config.
Looking to use Flex as a call-center solution with Google Contact Center AI as a backing integration for "AI" capabilities. In order to do that, I need to understand the integration between the two products better... more specifically, the same integration in this demo: https://youtu.be/n5vMhntiReg?t=2332
Al Cook describes it as a simple integration and a matter of "looping the call to Google", but it does not seem so trivial.
A user and an operator utilize Flex for the phone call. Flex then seems to stream the call to CCAI as a separate process to which the transcription/NLP processing and knowledge base information is returned to Flex.
How exactly do we setup this type of integration in Flex?
I am sure you guys have heard about Mozilla Firefox's LightBeam technology which graphically shows you the third party websites connected to your website. I would like to do something similar to that. Is there an API that I could use? Has anyone of you familiar with such an API?
Also, if there is something similar to Lightbeam that anyone of you might be using, then I'll appreciate if you can let me know.
Thanks.
Lightbeam (formerly Collusion) is an Add-on SDK extension, written in Javascript. I don't think it offers an official API you could interact with, and uses itself only APIs Firefox/Gecko provides plus some third party JS libraries such as d3.
But it is open source, so you're free to study the code, make pull requests and borrow stuff for your own projects.
Is the MetaWeblog API still supported? I ask because while researching XMLRPC, the Cook Computing library and implementing MetaWeblog API, I clicked a link that took me to MSDN that states the topic has been removed.
There is a link there that takes me to new docs for Windows Live SDK. On the new page i cannot find current info on MWAPI.
I am using EF, MV3, and VB.Net.
MetaWeblog API support had always seemed (to me) tenuous at best. Seeing as how the project hasn't been updated since 2003 (http://www.xmlrpc.com/metaWeblogApi) I think it is safe to assume that support has essentially ceased. That's my .02 anyway.
(Also, the Yahoo web group's newest post is from 2004 (http://tech.groups.yahoo.com/group/MetaWeblog-API/))