.NET Remoting over HTTP

[Looch]

All,

I currently have a windows application set up in a remote office that
accesses data via web services. This is a generic web servies set up
where the WebMethods exposed in an asmx file gather the data requested
and return a dataset.

I've been looking at Remoting and am wondering if there would be any
performance advantage to hosting remotable objects in IIS.

The benefits are obvious using Remoting over a LAN or WAN but is there
any performance gained by exposing remotable objects through IIS' web
services? Would that actually create more overhead?

Thanks for any input.

 

[Nicholas Paldino [.NET/C# MVP]]

Looch,

I don't think you will get any performance benefits. While I ^think^
that you might be able to use a binary encoding over an HTTP transport (I'm
not sure, you ^might^), the real benefits of hosting a remoting server in
IIS is to gain the benefits of IIS, namely authentication, app recycling,
etc, etc, not for performance.

 

[sloan]

Yeah, one of the main reasons to pick IIS with Remoting ... is that you
inherit all the IIS features without having to code them.
Aka, if the power shuts off or a reboot happens. IIS comes up.

Your alternative with Remoting..would be to write your own Windows Service.
That would have to startup on reboot.

And security, you can piggyback off of SSL with IIS, instead of handling it
yourself.

...

I think IIS is actually slightly slower. And you would pay the performance
penalty IN ORDER TO GET the piggyback features listed above.

Looch,

I don't think you will get any performance benefits. While I ^think^
that you might be able to use a binary encoding over an HTTP transport
(I'm not sure, you ^might^), the real benefits of hosting a remoting
server in IIS is to gain the benefits of IIS, namely authentication, app
recycling, etc, etc, not for performance.


--
- Nicholas Paldino [.NET/C# MVP]
- (e-mail address removed)

All,

I currently have a windows application set up in a remote office that
accesses data via web services. This is a generic web servies set up
where the WebMethods exposed in an asmx file gather the data requested
and return a dataset.

I've been looking at Remoting and am wondering if there would be any
performance advantage to hosting remotable objects in IIS.

The benefits are obvious using Remoting over a LAN or WAN but is there
any performance gained by exposing remotable objects through IIS' web
services? Would that actually create more overhead?

Thanks for any input.

 

[sloan]

The other key part is "DataSet". DataSet's don't serializer uber-well to
begin with.

....

You should look at WCF.

http://sholliday.spaces.live.com/Blog/cns!A68482B9628A842A!158.entry
(among other sites)

I would not code up a new project on Remoting these days. WCF is a better
alternative.

I also recommend Juval Lowy's book on WCF Services as well.

O'reilly. "Programming WCF Services".

 

[Doug Holland]

If possible though consider WCF services hosted within Windows Server 2008 /
Windows Vista with the Windows Activation Service. This will provide
significant benefits over and above using IIS 6.0 for hosting services.

Looch,

I don't think you will get any performance benefits. While I ^think^
that you might be able to use a binary encoding over an HTTP transport (I'm
not sure, you ^might^), the real benefits of hosting a remoting server in
IIS is to gain the benefits of IIS, namely authentication, app recycling,
etc, etc, not for performance.


--
- Nicholas Paldino [.NET/C# MVP]
- (e-mail address removed)

All,

I currently have a windows application set up in a remote office that
accesses data via web services. This is a generic web servies set up
where the WebMethods exposed in an asmx file gather the data requested
and return a dataset.

I've been looking at Remoting and am wondering if there would be any
performance advantage to hosting remotable objects in IIS.

The benefits are obvious using Remoting over a LAN or WAN but is there
any performance gained by exposing remotable objects through IIS' web
services? Would that actually create more overhead?

Thanks for any input.

 

[Mr. Arnold]

All,

I currently have a windows application set up in a remote office that
accesses data via web services. This is a generic web servies set up
where the WebMethods exposed in an asmx file gather the data requested
and return a dataset.

You can serialize the dataset to XML, use binary formatters, deserialize it
on the other side.

I've been looking at Remoting and am wondering if there would be any
performance advantage to hosting remotable objects in IIS.

If you want speed over the line, then binary over HTTP is faster that text
or SOAP.

The benefits are obvious using Remoting over a LAN or WAN but is there
any performance gained by exposing remotable objects through IIS' web
services? Would that actually create more overhead?

No, I don't think so.

Thanks for any input.

You can see it all in action if you want.

The binary over HTTP
The Web server with a Web service portal, and the Web server being used as
an implicit application server.
The .Net Remoting

http://www.lhotka.net/Default.aspx

 

[Looch]

Thanks for the replies, I've been looking at WCF...interesting.

 

[Nicholas Paldino [.NET/C# MVP]]

WCF is definitely a better option here, as it gives you fine-grained
control over pretty much every part of the process (from encoding, to
transport, to security, to interception, etc, etc). There is a lot of power
there, much more than remoting ever had, IMO.