[wp-xmlrpc] WP 2.2.1 breaks Ruby 1.8.2

Daniel Jalkut jalkut at red-sweater.com
Tue Jun 26 19:04:27 GMT 2007

On Jun 26, 2007, at 2:58 PM, Joe Cheng wrote:

> Actually, screw it--why shouldn't we prescribe exactly what the  
> behavior
> should be? Do server implementers really want flexibility here?? "The
> dateCreated MUST be in exactly yyyyMMddTHH:mm:ss format and SHOULD
> reflect the blog's local time zone if possible, and  
> dateCreatedTimeZone
> MUST specify the offset or Z if UTC." <= for getPost and getRecentPost
> only--there's different de facto behavior for newPost and editPost.

Sounds good to me. I agree it would be good to push servers to get rid  
of the Z from the dateCreated field since we know it breaks clients.

Fulfilling the "disambiguation" through an additional, newly defined  
XML attribute seems like a good path to continue pursuing. And I agree  
with you that now we've got some decent ideas on the table we should  
wait for Joseph and/or other WP peeps to chime in.

Thanks for brainstorming this with me,

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://comox.textdrive.com/pipermail/wp-xmlrpc/attachments/20070626/f3371278/attachment.htm

More information about the wp-xmlrpc mailing list