Re: Windows Service
I am curious about the security issue. Ingo Rammer, among others, recommends
hosting your remoted services in IIS. I agree with Bob 100%. If you have 2
..Net clients that need to communicate to each other, I would always choose a
remoting solution. Host remoted objects in IIS and use the binary formatter.
I would love to see any MS documents that say you should use web services in
preference to remoting when you do have 2 .Net clients communicating to each
other.
When Indigo arrives, by all means I would use that.
Dan
"Moty Michaely" wrote:
[color=blue]
> Hey Bob,
>
> I must argue with that :).
>
> I really think remoting has lots of disadvantages. Security is one of them.
> Since XML is still not Binary, remoting is the best way doing this kind of
> things, but if the 2 applications replace small amounts of data, textual xml
> and Web services enhancements doe's a great work with messaging technuiqes.
>
> Since I am in the middle of my project planning, I don't have to rearchitect
> any of the ideas. That's why I am asking you, the experts about the ways of
> dealing with this kind of project.
>
> Thanks again,
>
> - Moty -
>
> "Bob Grommes" <bob@bobgrommes .com> wrote in message
> news:OyeGkabdFH A.3328@TK2MSFTN GP09.phx.gbl...[color=green]
> > Moty,
> >
> > I'm amazed that a technology that less than 3 years ago was said to be the
> > Second Coming is now a "dead end". Not to put to fine a point on it,
> > that's horseshit.
> >
> > Remoting is a performant, extensible platform for IPC. I would use it
> > without hesitation anytime you have a .NET application at both ends of the
> > connection, complete control over the network / installation /
> > configuration at both ends, and don't anticipate that changing in the
> > foreseeable future. For example, I use remoting extensively (binary over
> > TCP/IP) to orchestrate a bunch of worker machines on the same subnet
> > performing various automated tasks.
> >
> > When communicating between clients and servers over the Internet to
> > locations you have no control over, or that operate on different platforms
> > than .NET) then you are generally stuck with Web Services over HTTP with
> > bulky XML payloads -- but you have a highly interoperable and flexible
> > standard, and it's arguably easier to implement and consume web services
> > than remoting. Although in my experience once you get over the config
> > issues remoting is no big deal to work with.
> >
> > Indigo is not out of development yet so it's not an option for the vast
> > majority of today's projects. Remoting may ultimately be deprecated in
> > favor or Indigo and may or may not find an ongoing niche of its own, but
> > it will be supported for a long time to come (a good decade or two is my
> > guess) even if it drops dead immediately upon Indigo's release, because
> > there are already a lot of released systems that use it, and for many if
> > not most of those there will be no compelling reason to rearchitect them
> > with Indigo since they work just fine as-is.
> >
> > --Bob
> >
> > "Moty Michaely" <moty@speedocs. co.il> wrote in message
> > news:OyHMIwadFH A.1276@tk2msftn gp13.phx.gbl...
> >[color=darkred]
> >> Remoting is one way but someone told me it's a dead-end and wse2 is the
> >> best way of dealing with these kind of things even in intranet areas.[/color]
> >
> >[/color]
>
>
>[/color]
I am curious about the security issue. Ingo Rammer, among others, recommends
hosting your remoted services in IIS. I agree with Bob 100%. If you have 2
..Net clients that need to communicate to each other, I would always choose a
remoting solution. Host remoted objects in IIS and use the binary formatter.
I would love to see any MS documents that say you should use web services in
preference to remoting when you do have 2 .Net clients communicating to each
other.
When Indigo arrives, by all means I would use that.
Dan
"Moty Michaely" wrote:
[color=blue]
> Hey Bob,
>
> I must argue with that :).
>
> I really think remoting has lots of disadvantages. Security is one of them.
> Since XML is still not Binary, remoting is the best way doing this kind of
> things, but if the 2 applications replace small amounts of data, textual xml
> and Web services enhancements doe's a great work with messaging technuiqes.
>
> Since I am in the middle of my project planning, I don't have to rearchitect
> any of the ideas. That's why I am asking you, the experts about the ways of
> dealing with this kind of project.
>
> Thanks again,
>
> - Moty -
>
> "Bob Grommes" <bob@bobgrommes .com> wrote in message
> news:OyeGkabdFH A.3328@TK2MSFTN GP09.phx.gbl...[color=green]
> > Moty,
> >
> > I'm amazed that a technology that less than 3 years ago was said to be the
> > Second Coming is now a "dead end". Not to put to fine a point on it,
> > that's horseshit.
> >
> > Remoting is a performant, extensible platform for IPC. I would use it
> > without hesitation anytime you have a .NET application at both ends of the
> > connection, complete control over the network / installation /
> > configuration at both ends, and don't anticipate that changing in the
> > foreseeable future. For example, I use remoting extensively (binary over
> > TCP/IP) to orchestrate a bunch of worker machines on the same subnet
> > performing various automated tasks.
> >
> > When communicating between clients and servers over the Internet to
> > locations you have no control over, or that operate on different platforms
> > than .NET) then you are generally stuck with Web Services over HTTP with
> > bulky XML payloads -- but you have a highly interoperable and flexible
> > standard, and it's arguably easier to implement and consume web services
> > than remoting. Although in my experience once you get over the config
> > issues remoting is no big deal to work with.
> >
> > Indigo is not out of development yet so it's not an option for the vast
> > majority of today's projects. Remoting may ultimately be deprecated in
> > favor or Indigo and may or may not find an ongoing niche of its own, but
> > it will be supported for a long time to come (a good decade or two is my
> > guess) even if it drops dead immediately upon Indigo's release, because
> > there are already a lot of released systems that use it, and for many if
> > not most of those there will be no compelling reason to rearchitect them
> > with Indigo since they work just fine as-is.
> >
> > --Bob
> >
> > "Moty Michaely" <moty@speedocs. co.il> wrote in message
> > news:OyHMIwadFH A.1276@tk2msftn gp13.phx.gbl...
> >[color=darkred]
> >> Remoting is one way but someone told me it's a dead-end and wse2 is the
> >> best way of dealing with these kind of things even in intranet areas.[/color]
> >
> >[/color]
>
>
>[/color]
Comment