Monoprocessing code on the client and server.,

Question

We are trying to come up with our client and server standard, and there is a lot of debate. One school of thought is the C # client server and java servers using some kind of proprietary messsage library to exchange data objects (I think the XML structure).

The problem with this model is that there is a lot of code that needs to be duplicated (validation, parsing) that could be reused if you went from C # to the server. If there is a big push for using a Linux machine, it won’t support your whole goal ..

Does anyone else have this dilemma?

Answer 1

There is a framework for this. ICE (ZeroC), protocol buffers, etc.

For example, my protocol buffer implementation (protobuf-net) runs on mono, MS.NET, CF, Silverlight, etc., and the binary format is compatible with various languages ​​(java, etc.). If you start with .proto (custom definition language), you can use it to create an object layer in each language you want.

Answer 2

In any case, I would use protocol buffers or something else defined in a language-neutral form for comments to ensure that you are not limited in the future.

Once you do this, you can start with C # in Mono. And then, if it turns out to be inoperative, you can switch to another language.

Answer 3

I would advise you to use some old, but good standard for transferring data between the two, SOAP and XML-RPC come to mind as examples for this. If possible or possible, you can try JSON or write your own XML format. Recently, quite a lot has been mentioned in protocol buffers, but I have not studied it, so I really can not say anything about it.

Answer 4

I will try to let the client and server run the same runtime (Java or CLR). We had great success using a combination of Mono and .Net client / Server.