Have you thought of repacking your Edit&Replay capability into a stand-alone tool able to edit-and-replay any request? I've been at a number of enterprises that have been such a tool homegrown but with limited…
May be a SOX requirement that requires auditable data be held for at least 7 years. I'd try again next year to truly check if it's "indefinite"
Looking at the code, I’m not seeing how you’re managaging the workflows/processes needed to manage ATS and ATP, along with reservations, within openship, the OMS.
what's the underlying technology that's powering the video meetings?
nice! are you willing to share the Imba code for us to learn from? and how was the debugging experience on Chrome? Was there a large barrier to go from compiled down JS code to Imba source?
Sounds like Elliptic Curve Diffie-Hellman is used between client/server to establish a private key. Not sure how this is new.
can I read about the tech as well?
fun!
Have you thought of repacking your Edit&Replay capability into a stand-alone tool able to edit-and-replay any request? I've been at a number of enterprises that have been such a tool homegrown but with limited…
May be a SOX requirement that requires auditable data be held for at least 7 years. I'd try again next year to truly check if it's "indefinite"
Looking at the code, I’m not seeing how you’re managaging the workflows/processes needed to manage ATS and ATP, along with reservations, within openship, the OMS.
what's the underlying technology that's powering the video meetings?
nice! are you willing to share the Imba code for us to learn from? and how was the debugging experience on Chrome? Was there a large barrier to go from compiled down JS code to Imba source?
Sounds like Elliptic Curve Diffie-Hellman is used between client/server to establish a private key. Not sure how this is new.
can I read about the tech as well?
fun!