Comments on: SoC: AtomPub Week 2 Status http://cavemonkey50.com/2008/06/soc-atompub-week-2-status/ Tech in the eyes of cavemonkey50. Thu, 14 May 2009 00:59:48 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Ronald Heft http://cavemonkey50.com/2008/06/soc-atompub-week-2-status/comment-page-1/#comment-83281 Ronald Heft Sat, 21 Jun 2008 04:00:03 +0000 http://cavemonkey50.com/?p=1407#comment-83281 Well, Toru, unfortunately the different endpoint made no difference. I'm still not able to pass authentication, even using the special API password. Do you know if MT is doing anything special outside of the traditional WSSE base64-encoded SHA1 hash password? Well, Toru, unfortunately the different endpoint made no difference. I’m still not able to pass authentication, even using the special API password. Do you know if MT is doing anything special outside of the traditional WSSE base64-encoded SHA1 hash password?

]]> By: Toru http://cavemonkey50.com/2008/06/soc-atompub-week-2-status/comment-page-1/#comment-83274 Toru Fri, 20 Jun 2008 06:17:54 +0000 http://cavemonkey50.com/?p=1407#comment-83274 I haven't tested MT since I did the last time. http://www.witha.jp/eXeries/2008/02/17/movable-type-41-and-atompub/ MT4.1 supports (kind of..) 2 kinds of AtomAPI. One was the old pre-draft version of AtomAPI, and another was the IETF's AtomPub. That's why MT4.1 had 2 endpoints. It took me a while to figure this out. Anyway, the SixApart dev team told me that they're gonna overhaul the code for the API like I posted to the blog. I haven’t tested MT since I did the last time.
http://www.witha.jp/eXeries/2008/02/17/movable-type-41-and-atompub/

MT4.1 supports (kind of..) 2 kinds of AtomAPI. One was the old pre-draft version of AtomAPI, and another was the IETF’s AtomPub. That’s why MT4.1 had 2 endpoints. It took me a while to figure this out.

Anyway, the SixApart dev team told me that they’re gonna overhaul the code for the API like I posted to the blog.

]]> By: Ronald Heft http://cavemonkey50.com/2008/06/soc-atompub-week-2-status/comment-page-1/#comment-83273 Ronald Heft Thu, 19 Jun 2008 15:30:06 +0000 http://cavemonkey50.com/?p=1407#comment-83273 There was no difference in using that URI. Have you been successful in using MT's Atom API? There was no difference in using that URI. Have you been successful in using MT’s Atom API?

]]> By: Ronald Heft http://cavemonkey50.com/2008/06/soc-atompub-week-2-status/comment-page-1/#comment-83271 Ronald Heft Thu, 19 Jun 2008 12:45:47 +0000 http://cavemonkey50.com/?p=1407#comment-83271 Toru, if that is the correct endpoint, then Movable Type is advertising the wrong URI in the RSD. Regardless, I'll try the URI you suggested and see if it makes any difference. Toru, if that is the correct endpoint, then Movable Type is advertising the wrong URI in the RSD. Regardless, I’ll try the URI you suggested and see if it makes any difference.

]]> By: Toru http://cavemonkey50.com/2008/06/soc-atompub-week-2-status/comment-page-1/#comment-83269 Toru Thu, 19 Jun 2008 09:27:52 +0000 http://cavemonkey50.com/?p=1407#comment-83269 Hi! Actually, if you are using AtomPub, correct endpoint is /mt-atom.cgi/1.0 Not /mt-atom.cgi/weblog So, in your case, http://mt.cavemonkey50.com/mt/mt-atom.cgi/1.0 And "the same cryptographic error message" seems to be a bug in MT. It suppors to display an error message such as invalid login. Hi!

Actually, if you are using AtomPub, correct endpoint is

/mt-atom.cgi/1.0

Not

/mt-atom.cgi/weblog

So, in your case,
http://mt.cavemonkey50.com/mt/mt-atom.cgi/1.0

And “the same cryptographic error message” seems to be a bug in MT. It suppors to display an error message such as invalid login.

]]> By: SoC: Week 3 Status · cavemonkey50.com http://cavemonkey50.com/2008/06/soc-atompub-week-2-status/comment-page-1/#comment-83234 SoC: Week 3 Status · cavemonkey50.com Sat, 14 Jun 2008 02:42:42 +0000 http://cavemonkey50.com/?p=1407#comment-83234 [...] started the week off by writing the custom XML parser I talked about last week. To do this, I researched several different methods for utilizing PHP’s xml_parse function. [...] [...] started the week off by writing the custom XML parser I talked about last week. To do this, I researched several different methods for utilizing PHP’s xml_parse function. [...]

]]> By: Ronald Heft http://cavemonkey50.com/2008/06/soc-atompub-week-2-status/comment-page-1/#comment-83195 Ronald Heft Sat, 07 Jun 2008 05:02:42 +0000 http://cavemonkey50.com/?p=1407#comment-83195 Yes, I'm well aware of SimplePie. However, it has been discussed in the past amongst WordPress developers that SimplePie should not be included in core. Regardless, writing a custom parser should be fairly straightforward, and will take less space than the whole SimplePie library. Yes, I’m well aware of SimplePie. However, it has been discussed in the past amongst WordPress developers that SimplePie should not be included in core. Regardless, writing a custom parser should be fairly straightforward, and will take less space than the whole SimplePie library.

]]> By: Joseph Scott http://cavemonkey50.com/2008/06/soc-atompub-week-2-status/comment-page-1/#comment-83194 Joseph Scott Sat, 07 Jun 2008 03:51:50 +0000 http://cavemonkey50.com/?p=1407#comment-83194 Have you tried SimplePie for ATOM parsing? http://simplepie.org/ Have you tried SimplePie for ATOM parsing?

http://simplepie.org/

]]>