talk@lists.collectionspace.org

WE HAVE SUNSET THIS LISTSERV - Join us at collectionspace@lyrasislists.org

View all threads

Switchover from from MIME multipart to pure XML services payloads now in place

AR
Aron Roberts
Wed, Feb 16, 2011 4:06 AM

As of tonight, resulting from Richard's work, the services layer now
sends and receives pure XML payloads (aka "Plain Old XML" or "POX"
payloads) over the wire.  These replace the MIME multipart message
payloads that the services have used more or less from their
inception.  Thanks to Chris, the application layer has been revised to
use this new payload format, as well.

These changes are now in place in the services and application trunk
(as of v.1.5), and on Nightly.  In a manually kicked-off run of the
Nightly Build, all services and app layer tests passed.  There is
still a possibility of some unforeseen issues cropping up; if you spot
any, please report these via JIRA.

This change was made to facilitate future services enhancements,
such as the ability to accept and return payloads containing multiple
records, to support import and other use cases.  In addition, for our
implementers who write their own client programs or scripts to access
CollectionSpace services, these new payloads should also be easier to
generate and consume.

Aron

As of tonight, resulting from Richard's work, the services layer now sends and receives pure XML payloads (aka "Plain Old XML" or "POX" payloads) over the wire. These replace the MIME multipart message payloads that the services have used more or less from their inception. Thanks to Chris, the application layer has been revised to use this new payload format, as well. These changes are now in place in the services and application trunk (as of v.1.5), and on Nightly. In a manually kicked-off run of the Nightly Build, all services and app layer tests passed. There is still a possibility of some unforeseen issues cropping up; if you spot any, please report these via JIRA. This change was made to facilitate future services enhancements, such as the ability to accept and return payloads containing multiple records, to support import and other use cases. In addition, for our implementers who write their own client programs or scripts to access CollectionSpace services, these new payloads should also be easier to generate and consume. Aron