xml web services vs .net remoting

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Joe

    #1

    xml web services vs .net remoting

    Question
    1.) Since xml web service interface can be obtained directly by wsdl, but
    ..net remoting need to have the dll (interface) and then take reference to the
    solution, right?
    2.) remoting need to be the same intranet?
  • Mehdi

    #2
    Re: xml web services vs .net remoting

    On Wed, 3 Aug 2005 01:56:04 -0700, Joe wrote:
    [color=blue]
    > Question
    > 1.) Since xml web service interface can be obtained directly by wsdl, but
    > .net remoting need to have the dll (interface) and then take reference to the
    > solution, right?[/color]

    Yes, with .NET Remoting you need to have the interface of the remoted
    objects in a DLL referenced by both the server and client applications.
    There are other ways to access a remote object through .NET Remoting
    without this shared DLL, but having never experienced them, i couldn't tell
    you how they work.
    [color=blue]
    > 2.) remoting need to be the same intranet?[/color]

    Not at all. We at the moment have an application with the server hosted on
    our LAN and the client applications a bit everywhere on the Internet. It
    works just fine (although if you want to do that, you should probably have
    a look at Genuine Channels to avoid the firewall/proxy problems when making
    callbacks from the server to the client: www.genuinechannels.com).

    Comment

    Working...