Robert Buchanan, API Evangelist at Procter & Gamble
Oh, absolutely. And I mean, a lot of people go and quote, you know, um, they seem to be spec and like, well, you know, gets don't deserve bodies. Okay. But query is a new RFC that's out there for a new method. It is effectively a get with a body because it's doing all the semantics of what we use post for for searching, but it's putting it into a way that you can do it over a query method, which is a subset of what get did. So, you know, we are creating new RFCs for new endpoints, but I think it's, those are great for like the global standards, but I think companies in general should be able to draft their own for their own company canonical use, because it would expand a lot of what we're doing inside of APIs. And it also, you know, Start to blend when we need things like GRPC, which are very action oriented, very process oriented things, you know, and there's benefits to use GRPC for their low latency and their low or their fast transmission and whatnot. But realistically, we could take some of those learnings and say we can apply those to even RESTful endpoints because we have the other verbs to describe what we're doing. I think it's a miss in the industry and sadly. Changing OpenAPI spec isn't enough because a lot of the vendors, like, uh, the CDNs out there, the gateways out there, they restrict you. In fact, um, I submitted an issue to the Zig programming language because their first implementation of an HTTP server at the core language only supported certain verbs. I said, well, the spec says this and they actually went through and change it. I love the, the Zig Dev team. Cause they went through with a lot of feedback from the community, went and changed it to where you can now supply custom verbs inside their core system.
