Should the translation of a message occur on the server side or on the client side?
I, as a customer, have the right to look for the best service provider.
And if that provider speaks my own language, better business will be done.
Let's say that I need some info from a weather service, but happens to be that my client is a web page, or a C#, python or ruby app.
Why should I take the burden to parse that xml message just because it is considered standard?
What if the provider and I previously agreed in the format exchange?
If the provider could send me the data as a C# binary serialized stream, or a javascript or ruby source stream, then any parsing would be unnecessary, for the message could easily be converted to an object for direct consumption by the client.
If I need a jpeg, I get a binary stream as a jpeg, not an useless xml message.
If I decide to have xml, good for me, freedom of choice should prevail. But I guarantee you that after the world has seen other formats than xml, nobody will ever look back.
Pick your flavor, what kind of SODA you want to drink today?
// C# - Java
Employee{
Name="John Doe";
Salary=99876.54;
isActive=true;
}
' VB
Employee
Name="John Doe"
Salary=99876.54
isActive=true
End
// Javascript
Employee{
Name:"John Doe",
Salary:99876.54,
isActive:true
}
Envelope:
Header:
ContentType=Javascript // here you define the language you speak
Body: {stream}
I don't know esperanto and don't want to learn it, clear ?