none
.Net remoting RRS feed

  • Question

  • Hi,

    why .net remoting is platform dependent ? what internal work happens, when two process communicates ?


    Thursday, September 12, 2013 8:26 AM

Answers

  • Technically remoting can be implemented on any system that supports TCP sockets. In fact it doesn't even need TCP sockets since it's protocol/transport layer independent (remoting = top 3 layers of OSI). So under the hood you'll simply find a pair of TCP sockets, most of the time...

    There are plenty of 3rd party remoting channels that allow interfacing with other interprocess communication technologies, check out this link for a remoting to CORBA channel http://remoting-corba.sourceforge.net/.

    The main issue with remoting would be that it's proprietary and not standardized, MS can change/break it whenever they feel like it (and in fact they did just that by launching WCF (no idea why, there was/is nothing wrong w remoting)).

    Monday, September 16, 2013 6:22 AM
  • Hi Alavudeenbatcha,

    Thank you for posting in the MSDN forum.

    This forum is to discuss problems of .NET Framework Class Libraries. Your question is not related to the topic of this forum. The .NET Remoting and Runtime Serialization forum was archived, but you can ask .NET Remoting issue in the WCF forum now, to help you resolve this issue as soon as possible and get other community members’ active participation for this issue, I would suggest you post a new thread in WCF forum where you can contact the WCF experts. You could post this thread’s link in your new thread, so we could know more information from the previous replies, you could also share us the latest information about this issue in your new thread.

    WCF forum

    http://social.msdn.microsoft.com/Forums/vstudio/en-US/home?forum=wcf

    Sorry for the inconvenience caused to you.

    If there's any concern, please feel free to let me know.
    Sincerely,

    Damon


    <THE CONTENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, WHETHER EXPRESS OR IMPLIED>
    Thanks
    MSDN Community Support

    Please remember to "Mark as Answer" the responses that resolved your issue. It is a common way to recognize those who have helped you, and makes it easier for other visitors to find the resolution later.



    Monday, September 16, 2013 6:55 AM

All replies

  • Hi,

    For these issues, I would suggest you have a look at the references below.

    http://msdn.microsoft.com/en-us/library/ms973864.aspx

    http://msdn.microsoft.com/en-us/library/2e7z38xb(v=vs.85).aspx

    http://msdn.microsoft.com/en-us/library/kwdt6w2k(VS.71).aspx

    I will share some information here.

    The Microsoft .NET Framework provides a powerful, extensible, and language-independent framework to develop robust and scalable distributed systems. The .NET Remoting Framework provides powerful ways to remote interaction depending on the requirement of the system. .NET Remoting integrates seamlessly with Web Services and provides a way to expose .NET objects for access across multiple platforms.

    Cross-process communication requires a server object whose functionality is provided to callers outside its process, a client that makes calls on the server object, and a transportation mechanism to ferry the calls from one end to the other. The addresses of server methods are logical and function properly in one process, but do not function in a different client process. To alleviate this problem, a client can call a server object by making a copy of the object in its entirety and moving it to the client process, where the copy's methods can be invoked directly.

    Regards


    ALL FOR ONE AND ONE FOR ALL.

    Friday, September 13, 2013 6:32 AM
  • What makes you think it's platform dependent?

    Mono/xamarin implements it and it works just fine on linux/mac last time I checked.

    Friday, September 13, 2013 11:20 AM
  • Hi,

    Thanks for your response.

    "Mono/xamarin implements it and it works just fine on linux/mac last time I checked."

    Mono/xamarin used for cross platform support irrespective of what platform you have used for your application development. my question is, why .net remoting is platform dependent ex: we use webservice to acheive platform independent. what is the blocking case for remoting ? what internal work is happening when remoting between two process ? why other system can't understand my remoting request send from one platform to another platform ?
    Sunday, September 15, 2013 5:52 AM
  • Technically remoting can be implemented on any system that supports TCP sockets. In fact it doesn't even need TCP sockets since it's protocol/transport layer independent (remoting = top 3 layers of OSI). So under the hood you'll simply find a pair of TCP sockets, most of the time...

    There are plenty of 3rd party remoting channels that allow interfacing with other interprocess communication technologies, check out this link for a remoting to CORBA channel http://remoting-corba.sourceforge.net/.

    The main issue with remoting would be that it's proprietary and not standardized, MS can change/break it whenever they feel like it (and in fact they did just that by launching WCF (no idea why, there was/is nothing wrong w remoting)).

    Monday, September 16, 2013 6:22 AM
  • Hi Alavudeenbatcha,

    Thank you for posting in the MSDN forum.

    This forum is to discuss problems of .NET Framework Class Libraries. Your question is not related to the topic of this forum. The .NET Remoting and Runtime Serialization forum was archived, but you can ask .NET Remoting issue in the WCF forum now, to help you resolve this issue as soon as possible and get other community members’ active participation for this issue, I would suggest you post a new thread in WCF forum where you can contact the WCF experts. You could post this thread’s link in your new thread, so we could know more information from the previous replies, you could also share us the latest information about this issue in your new thread.

    WCF forum

    http://social.msdn.microsoft.com/Forums/vstudio/en-US/home?forum=wcf

    Sorry for the inconvenience caused to you.

    If there's any concern, please feel free to let me know.
    Sincerely,

    Damon


    <THE CONTENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, WHETHER EXPRESS OR IMPLIED>
    Thanks
    MSDN Community Support

    Please remember to "Mark as Answer" the responses that resolved your issue. It is a common way to recognize those who have helped you, and makes it easier for other visitors to find the resolution later.



    Monday, September 16, 2013 6:55 AM