Aaron, I’ve been taking cues from your talk here, for setting up a listener that creates new posts when asked to by an external web app. It’s working fine, and I’m using your suggestions here for handling authentication (checking a salted-secret). The request is coming in as a POST with a Content-Type: application/x-www-form-urlencoded header.
Now, I’m looking into sending the data as json, with a Content-Type: application/json header. This seems to be the way it’s encouraged by the jetpack JSON API, and I guess oAuth2 should be used to authenticate.
How does that approach relate to the methods you’re suggesting here, and would you recommend using the JetPack JSON API instead of the approach you’ve outlined here?
For me, I’m able to follow and apply the method you show here, whereas utilising the JSON API and especially oAuth2 would require another trip up the learning curve 🙂
Medley
WordPress.tv 
February 6, 2013 at 1:40 pm |
Aaron, I’ve been taking cues from your talk here, for setting up a listener that creates new posts when asked to by an external web app. It’s working fine, and I’m using your suggestions here for handling authentication (checking a salted-secret). The request is coming in as a POST with a Content-Type: application/x-www-form-urlencoded header.
Now, I’m looking into sending the data as json, with a Content-Type: application/json header. This seems to be the way it’s encouraged by the jetpack JSON API, and I guess oAuth2 should be used to authenticate.
How does that approach relate to the methods you’re suggesting here, and would you recommend using the JetPack JSON API instead of the approach you’ve outlined here?
For me, I’m able to follow and apply the method you show here, whereas utilising the JSON API and especially oAuth2 would require another trip up the learning curve 🙂
LikeLiked by 1 person