Re: Disadvantages/Cons of web services?

From: William Stacey [MVP] (staceywREMOVE_at_mvps.org)
Date: 01/17/05 

Date: Mon, 17 Jan 2005 11:41:43 -0500

Your types are bound at both sides. So if you change a return class (for
example) or add something you need to change all the clients. With xml, you
can send document containing a,b,c,d even if service only uses a,b. Or
return a,b,c,d even if your client only needs a. Also, you can get any type
into XML, which is not always true with remoting. So things are a lot more
flexible. Others may have better examples for you. 

-- 
William Stacey, MVP
http://mvp.support.microsoft.com
"Jon Paugh" <anonymous@discussions.microsoft.com> wrote in message
news:1a9301c4fca6$74346ce0$a401280a@phx.gbl...
> Hi,
>
> Please explain what you mean by the "versioning issues"
> with .NET remoting,
>
> Thanks,
>
> Jon Paugh
>
> >-----Original Message-----
> >I don't really see any.  In reality (in a MS world) you
> have socket,
> >Remoting, and WS/WSE.  If you use raw sockets, you end
> up reinventing much
> >of what is already their in web services.  Today, I
> think the decision point
> >is if to use WSE or plain IIS web services.  With WSE
> you get all the
> >security stuff (and other WS-xxx) and can "touch" it if
> you have special
> >needs.  With WS you can automatic broad reach for your
> SOA, even if you
> >don't expose it right away.  Also, you have server tools
> like SQL and
> >BizTalk that all use xml web services so you can
> integrate with those. Also
> >you will be in good position for Indigo if it ever goes
> RTM.  In a MSDN
> >video I saw, Don Box asked the audience if anyone had
> successfully rolled
> >out a Enterprise Remoting app and *nobody raised there
> hands.  Remoting is a
> >great tech, but is not the future and versioning issue
> pretty much is the
> >killer IMO.  WS is now and the future so the case should
> be "what should I
> >use if not Web services?".  That would depend on your
> needs.
> >
> >-- 
> >William Stacey, MVP
> >http://mvp.support.microsoft.com
> >
> >"EmJayEm" <Woo@eookie.com> wrote in message
> >news:5ObGd.141236$48.126997@fe1.news.blueyonder.co.uk...
> >> Can you give any disadvantages of web services then?
> >>
> >>
> >
> >.
> >

Relevant Pages

  • Workaround with Remoting in CF
    ... I know that CF doesn't support .NET Remoting but, does Web Services support ... I need a hash table in memory and clients accesing to it. ... The problem with WS is that I can't have the table in memory. ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: Common Component Deployment Options
    ... The physical deployment of a component is highly dependent on the type ... provides common services and functionality to all clients, ... most cases id suggest using Web Services over .Net Remoting. ...
    (microsoft.public.dotnet.framework.remoting)
  • Re: Remoting vs Web Services
    ... very important issues.Basically,our clients will be used as POS terminals..we ... Remoting does have a lot of issue and should not be ... > used without careful consideration, but banning them outright from consideration is not a good idea. ... >> go with Web Services. ...
    (microsoft.public.dotnet.distributed_apps)
  • Re: Yet another, remoting vs web services, datasets vs custom objects....
    ... >> Ive used Web Services in anger for over 4 years since M$ SOAP Toolkit v1, ... >> Compared to Remoting Im told they are slower (serialise and deserialise I ... You should prefer XML since it offers maximal interoperability. ...
    (microsoft.public.dotnet.distributed_apps)
  • Re: Disadvantages/Cons of web services?
    ... clients. ... >into XML, which is not always true with remoting. ... >> have socket, ...
    (microsoft.public.dotnet.framework.webservices)