> That's how things used to work, but it was unreliable and couldn't > deal with arrays containing zero or one elements. I'm the author of > the patch that added the type="array" attribute, and I did think > about how to deal with the backward compatibility. I just couldn't > figure out how to do it reliably (which was the whole problem with > that approach in the first place), so I punted.
Ok, I didn't think of that. > From what I've heard, ActiveResource and the ActiveRecord xml code > is meant more for closely coupled client/server interaction than > building a generic public XML API, but that's just hearsay and could > be wrong. Well, I thought REST in it's nature was supposed to be loosely coupled, but I might be wrong too... > However, if you want Rails to interoperate with other > systems, it's probably time to think about embracing an existing > standard. I don't know of any widely adopted RESTful XML API > standards. Do you? Not really, and I see this as one of the major problems with REST these days. Axis2 provides REST support - maybe we should look at their stuff? The XML-RPC guys created a spec a few years ago that tried solving similar issues by defining a spec: http://www.xmlrpc.com/spec Maybe the rails way should become the standard? In that case it would make sense to create implementations in other languages as well. Cheers, Stefan -- Bekk Open Source http://boss.bekk.no --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
