Phase System TM Web Service

You are great

Sir, Very well explained. Thanks.

Great overview! Do you have any books or other resources you can recommend on the topic?

A high quality content! Thank you very much.

I completely agree with you - I was thinking about getting the new one , since it just launched but having no API or Zapier/Make connection really limits my willingness to buy it. Your video is now 3 years old, am I missing something? - Is there an API available now?

Really good thanks

Brilliant explanation thanks 🙏

Thank you for a great talk with useful visuals! I make a Unix program (durdraw) for drawing Unicode and other text art, and find myself working with different character encoding regularly. Perhaps I missed it, but Utf-8's backwards compatibility with ASCII is worth considering when choosing an encoding scheme. I also liked the useful "od" syntax. I rarely encounter Utf-16, but thanks to your video I will now be able to recognize it in a hex dump.

Can you list some specific API tools that you mentioned in the video in general?

so China will win with us even easier, we will be their beef cattle

Thanks

those JSON schemas are used a lot in Kafka to read from topics that are JSON encoded, at least some familiar to me

thanks, very interesting video

Thanks, helped me to understand finally difference between microservices and API

Plz speak little slowly...

Thank you

As someone who wants to transition from UX to technical writing, which would be most appropriate to learn? For API documentation

Thank you for the great content

Nicely explained, thank you

Very informative video, I am going through Ikenna Nwaiwu books and it has been a gold mine.

Nice

Wow

best explanation ever heard out

Thanks for sharing that!

Very appreciative! Good info!

Thanks for having us on!

Great video.

Thank you so much!

Please how do I find encoding of my file

If you have a CPU where every address is 16 bits wide, you may as well use UTF-16 as default. If memory is 8 bits wide, use UTF-8. For 32 bit (or 64 bit) you can store multiple characters per RAM address, no matter what system you choose.

Thank You Sir💌

Interesting. 😃👍

👍

Great inspiration. I like the idea to add greasing to an API gateway.

Amazing, straight forward, here in India just to explain same thing people making 1hr or quite longer video so when we reach to end of the video we forget what the actual question was

Clear explanations, amazing video! Thanks!

I keep getting these videos that talk about making something work,but they don't start or end with a demo.🙄

Thanks for this video. I’m currently working on a project that needs some data, basically lists of protocols for radiation therapy plans. I wanted to avoid adding a database initially, so I created the protocols in a plain text document using xml. But over the last week I’ve been thinking json would probably have been better. Your video pushed my 100% there. Will be converting xml to json. May even bite the bullet and create the database.

How?

Excellently explained. Thank you.

The tools is very nice however it does not handles OAS 3.1 (ticket open since 4 years) 🤕

Danke!

Very well explained. Thank you for making this video!

so is WebService and REST API the same? Or is REST a "type" of WebService? what are others? or vice versa?

I liked your video halfway through watching it. Good work.

thanks for making this! Very helpful 👍

Great content. Thanks

I followed the installation steps for spectral and created .spectral.yaml file which contains extends: spectral:oas but running the spectral lint command gives below error. Error #1: Invalid ruleset provided .spectral.yaml file is at the current directory where I am running the spectral lint command as below. spectral lint <full file path>/openapi.yaml Can you help me get rid of this error?

Except in very specific, limited ways, it is a horrible principle, which has poor unintended consequences. In most circumstances, interfaces should loudly reject bad inputs. What we don't want is unpredictable behavior on bad input, like crashing, or worse, an exploitable security hole. Robustness means withstanding bad inputs. But programs should not try to repair bad input, meaning trying to turn it into good input which is then accepted and acted on.