In the future, we might want to have a generic non-serializable Artist model, then have separate models for each version that serialize to XML. There may be a system for automatically selecting the correct serialization model based on the version supplied in the request URL.
Originally posted by @yoshiask in #14 (comment)
The current system uses the same model for both passing data and serializing to XML. This has been mostly fine but poses a few issues, the most immediately problematic being that the XML model may vary between API versions or clients. Creating separate data and serialization models may simplify the controllers once we start supporting older/different versions of the API.
Originally posted by @yoshiask in #14 (comment)
The current system uses the same model for both passing data and serializing to XML. This has been mostly fine but poses a few issues, the most immediately problematic being that the XML model may vary between API versions or clients. Creating separate data and serialization models may simplify the controllers once we start supporting older/different versions of the API.