scottbarstow
commented
9 years ago @sachanacar
To put more meat on the bones Ivelin talked about, we've discussed allowing users the ability to write code within RVD apps and execute the code in a "jailed" environment that only provides access to core APIs in a unique way.
Would be great to kick this around with you when you have a few minutes.
As to a starting point, I have a fork of Twilio node lib that actually works rudimentarily with Restcomm already. I'll see if I can locate it and check the current state. If worthwhile I'll forward.
On Mon, Aug 31, 2015 at 10:51 AM, ivelin notifications@github.com wrote:
@sachanacar https://github.com/sachanacar , here is a reference point: http://twilio.github.io/twilio-node/
Licensed under MIT. Feel free to fork it as a starting point. https://github.com/twilio/twilio-node
A topic for a separate issue but still related is the use of JS in RVD. Currently RVD allows drag&drop and basic regex with variables. It has been an open topic if, when and how we should enable a more liberal access to underlying APIs within RVD. Creating a node.js SDK for Restcomm brings us closer to the answer.
— Reply to this email directly or view it on GitHub https://github.com/Mobicents/restcomm-sdk-node/issues/1#issuecomment-136396306 .
scottbarstow.com @scottbarstow +1-919-349-9473 (m)
sachanacar
@sachanacar , here is a reference point: http://twilio.github.io/twilio-node/
Licensed under MIT. Feel free to fork it as a starting point. https://github.com/twilio/twilio-node
A topic for a separate issue but still related is the use of JS in RVD. Currently RVD allows drag&drop and basic regex with variables. It has been an open topic if, when and how we should enable a more liberal access to underlying APIs within RVD. Creating a node.js SDK for Restcomm brings us closer to the answer.