Given that both the client and the server need to know everything about the object being remoted, firstly is this tight coupling, and secondly can .Net Remoting work in any other way?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Given that both the client and the server need to know everything about the object being remoted, firstly is this tight coupling, and secondly can .Net Remoting work in any other way?
Not really answering your question, but if you want to loosen the coupling, you might look at WCF’s NETTCP binding as an alternative. The client can create a proxy for the entities – this way you won’t need to share any assemblies (notably Entities) between client and server.