Re: Real Basic Stuff

From: Sunny (sunnyask_at_icebergwireless.com)
Date: 04/16/04


Date: Fri, 16 Apr 2004 12:17:55 -0500

Hi david,
read inline:

> Hmmm. Would it be better to implement a methods MBR object "Customers"
> (with GetCustomer(), UpdateCustomer() as exposed methods etc...) which
> returns and consumes an MBV object "Customer" (with all the
> customer-specific properties and methods exposed). The MBV object could
> then be used on the client.

The Consumer object can be passed and received from a web service also.
The real difference is:
1. Web services use only XML SOAP serialization over HTTP, and are
hosted in IIS
1.1. They are good for sharing data between different platforms.

2. With remoting you can also use a binary serialization (much faster)
and TCP channels, also much faster.
2.2. Proprietary channels and formatters, so good only for .Net
client/servers.

> Thing is, the MBV object created by the WebService is a very shallow
> instance of the object "CustomerProxy" (ie: simply a collection of fields).
> Is there a simple way of taking a proxy object and deserializing it into an
> instance of the original object (the Base class library will be included in
> the Winforms client) which can be manipulated by the client software and
> then passed back as an argument in another WS call? If there is, WS is my
> architecture of choice; if not Remoting is the way forward.
>

You can control the serialization both in remoting and web service, so
you can get what you need.

Sunny



Relevant Pages

  • Re: Sending Messages and Sharing Objects
    ... RJ> are using CSLA framework by Rocky because it allows us to switch ... Web Service, Remoting or Simple ... RJ> since client requirements could vary. ... RJ> to use any of the channels - 2Tier, Web Service or Remoting ...
    (microsoft.public.dotnet.distributed_apps)
  • Re: asp.net webservice design/ component issue
    ... > to share a single object while at the same time insulating the client ... > I'd like to avoid deploying the remoting objects as web services ... a client of a remoting web service needs to be aware ...
    (microsoft.public.dotnet.framework.aspnet.webservices)
  • Re: Pushing data from the server to the client
    ... >> your client that listens.. ... it hits your web service or uses remoting. ... So I mocked up a facade web service on my side in .NET ... >> connection with Remoting, so you'd also have a practical limit based on ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Pushing data from the server to the client
    ... >> your client that listens.. ... it hits your web service or uses remoting. ... So I mocked up a facade web service on my side in .NET ... >> connection with Remoting, so you'd also have a practical limit based on ...
    (microsoft.public.dotnet.framework.webservices)
  • Re: Pushing data from the server to the client
    ... >> your client that listens.. ... it hits your web service or uses remoting. ... So I mocked up a facade web service on my side in .NET ... >> connection with Remoting, so you'd also have a practical limit based on ...
    (microsoft.public.dotnet.framework.remoting)

Loading