I just mentioned a moment ago that we like standards.
We like standards, you know, if it I don't want to have to build a custom a p I to communicate for every application that I have on the network, every application that I want on the Internet
Now the problem with that is often when a vendor comes up with an application, they're so proud of themselves for that application, they like to develop their own custom. A p I. This is how you connect with us on this. The only way you can connect with us because we're so awesome. We do our own things
now. What that means is on a network administrators perspective, I've gotta develop
or I've got to utilize a proprietary A p I. And you can see it in this illustration. The slide show. And you know, I'm not saying that office has proprietary AP eyes or any of these, but you can see the problem if
I've got all of these service is that can use a standard
ap I skim and S P M. L. As opposed to proprietary. What vendors should want to do is make the case load easier on administrators. While I'm like an implement products that just make my life harder,
especially in the world today, that if you're looking for service there are 11 million different companies that can provide a comparable service.
I'm personally going to choose the one that provides the same function. That's easier for me to use. So again, just this idea that, you know, we've got some native support for standards based AP eyes. That's what we would be looking for proprietary causes. More work on the network admin.