This is the reason that the spec for patch[1] specifically requires a diff be sent[2]:
> The set of changes is represented in a format called a "patch > document" identified by a media type. and > With PATCH, however, the enclosed entity contains a set > of instructions describing how a resource currently residing on the > origin server should be modified to produce a new version. and > Further, it is expected that different patch document formats will be > appropriate for different types of resources and that no single > format will be appropriate for all types of resources. Therefore, > there is no single default patch document format that implementations > are required to support. If you plan to use PATCH, you should figure out what you need and use it. I'm not aware of a media type that does diffs in plain JSON at this time. 1: http://tools.ietf.org/html/rfc5789 2: http://tools.ietf.org/html/rfc5789#section-2 -- 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.
