Reply to thread

Message

<blockquote data-quote="samuel337" data-source="post: 88372" data-attributes="member: 10347">I left out the extra serialise/deserialise step for clarity, but you're right. Anyway, the system you described above is how MPBlue does it. Problem is, if at any time the MP devs decide to change something which changes how the MP equivalent object works, the web service would either result in an error, or malfunction. (Unless you access the database directly via SQL, which then makes you vulnerable to database schema changes.) In any case, there will probably be need for a new version, which needs to be tested all over again etc.That said, because MP's music database class is in such a mess because direct SQL statements are used instead of the DAL, I've had to create some new objects too for specific information (e.g. for things like Album and Artist) that get the information by accessing the database directly.In the end its a compromise between making things easier for the .NET devs (by using generics etc.) or making things more accessible to everyone (e.g. using arrays instead of generic lists).Some profiling of this would be interesting.Sam</blockquote>

[QUOTE="samuel337, post: 88372, member: 10347"] I left out the extra serialise/deserialise step for clarity, but you're right. Anyway, the system you described above is how MPBlue does it. Problem is, if at any time the MP devs decide to change something which changes how the MP equivalent object works, the web service would either result in an error, or malfunction. (Unless you access the database directly via SQL, which then makes you vulnerable to database schema changes.) In any case, there will probably be need for a new version, which needs to be tested all over again etc. That said, because MP's music database class is in such a mess because direct SQL statements are used instead of the DAL, I've had to create some new objects too for specific information (e.g. for things like Album and Artist) that get the information by accessing the database directly. In the end its a compromise between making things easier for the .NET devs (by using generics etc.) or making things more accessible to everyone (e.g. using arrays instead of generic lists). Some profiling of this would be interesting. Sam [/QUOTE]

Verification