A Christ-follower, husband, father, and WordPress Developer with Forum One.
The Simple Guide to HTTP Verbs: PATCH, PUT, and POST – DZone Integration
J Andrew Scott – http://rubberchickenfarm.com/ History of APIs RSS Advantages Fast & reliable Easy to consume Almost no technical footprint Disadvantages Read-only Static content No authentication No user-driven content (i.e. comments, favorites, etc) DIY API Advantages Dynamic content User-driven content App & user authentication Roles & permissions based Connected applications Disadvantages DIY OAuth Redundant URI scheme Mediocre performance Large technical footprint WP-API Advantages Succinct URI scheme Improved performance Small technical footprint Available in WordPress core Disadvantages Granular transactions No batch uploads Increased number of API calls What once required 2 web servers now required 12-15 servers WP-API Disadvantage Factors & Solutions Number of content types Solution: consolidate endpoints Volume of individual API calls Solution: batch processing endpoints Frequency of individual API calls Solution: page-level caching Lessons…
After some conversation with others on #Mastodon about other caching issues with #ActivityPub & #WordPress it was revealed that it came down to the Accept headers being received by requests to the caching services. The caching services could be things like #Cloudflare or web servers such as #OpenLiteSpeed, or even WordPress caching plugins. In my case I use the OpenLiteSpeed web server caching and I started digging into how caching works in OpenLiteSpeed and how I could fix it for my WordPress site.
I love this guide from Aaron on keys to maintaining a solid SCM history.
As a developer there are industry standards and expectations that should be followed, especially in the open source world. Aaron Jorbin has got this spot on.