Thank you, This is a promising technology. I'll be willing to help in any way, I'm a vuejs / javascript developer and designer, and also a documentary filmmaker and video editor. Let me know if I can help in promoting this tech. I can probably use this tech in my Cleanvid project. cleanvid.org, the site is not done yet.
Software Engineer, then father, then CTO, then father again, then cofounder, then CEO, then MBA, then success, then crash, then freelance and then CMO at
@scaledynamics
Software Engineer, then father, then CTO, then father again, then cofounder, then CEO, then MBA, then success, then crash, then freelance and then CMO at
@scaledynamics
Hi Sophek, actually WarpJS does not expose an HTTP REST API on top of the function. It uses its own protocol to wrap the function parameters (that may not be primitive types) and required context elements to run it serverless. When done, it returns also the result (again, maybe an object) to get back to the awaiting front-end context. Both frontend and backend need to be coded in JavaScript, but you can use any framework.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thanks for this tutorial. Quick question how do I consume the serverless function apart from warpjs?
const hello = (name) => {
// warp directive
'warp +server -client'
return
Hello ${name} from Node.js ${process.version}}
Could I go to xxxxxxxx.url/hello? or something?
Thank you, This is a promising technology. I'll be willing to help in any way, I'm a vuejs / javascript developer and designer, and also a documentary filmmaker and video editor. Let me know if I can help in promoting this tech. I can probably use this tech in my Cleanvid project. cleanvid.org, the site is not done yet.
Thank you for your proposition :) That's awesome. Let's talk in private then.
Hi Sophek, actually WarpJS does not expose an HTTP REST API on top of the function. It uses its own protocol to wrap the function parameters (that may not be primitive types) and required context elements to run it serverless. When done, it returns also the result (again, maybe an object) to get back to the awaiting front-end context. Both frontend and backend need to be coded in JavaScript, but you can use any framework.