Re: Is Remoting The Right Tool For My Job?



I would still go Web Services. It is pretty simple to maintain and has
visibility on management interfaces and applications, rather than remoting
(you could, but you would need to implement a lot of instrumentation for
that). If your classes (data classes, business entities, etc) won't
serialize, is there any possibility you could change them? Remember that
even on remoting, you need to serialize your objects - there is a little bit
different because you can serialize your objects to binary also.

There are lot of ways to do what you want. You could serialize your objects
to binary and pass them as a MIME/DIME attachment to the web service. On the
other side, you would open the attachment and de-serialize the object from
the binary data you received. This would work for you, no doubt. But, it is
a workaround for sure.

I would rather understand and investigate the cause why your objects won't
serialize first. Even going remoting, this may get you sometime.

--
Regards,
Robson Siqueira
Enterprise Architect

"senfo" <enceladus311@xxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:OjgHjd4HHHA.1248@xxxxxxxxxxxxxxxxxxxxxxx
I wrote a Windows application that used a custom DAL (data access layer) to
perform all database calls for the application. The problem is that the
application is run as the current user and the client (customer) does not
wish to grant permission to the database for individual users, even if
permission is granted through a group & role. We came up with a viable
solution that would mean separating the DAL into a web service that is
hosted by IIS and runs under a user which only key administrators have the
password for. That way users could pass credentials on to the web service
and the web service could decide whether or not the user had access to the
services; but, it would be impossible for the user to gain direct access to
the database. It sounded like a promising idea to convert my original DAL
into a web service until I realized that the properties in my classes would
not be serialized as XML. That's when I started thinking that it might be
a better idea to use .NET Remoting since I can assure that my client will
only be written in .NET.

Anybody have any opinions? Does .NET Remoting sound like the right tool
for the job?

On a side note, Windows Communication Foundation is not yet permitted.

Thank you in advance,

--
Sean


.



Relevant Pages

  • Re: Serialization Exception
    ... remoting layer is attempting to serialize the SoapException across the ... remoting boundary, which in this case is a process boundary. ... I have a web service application that works fine, ... call the System Tray application. ...
    (microsoft.public.dotnet.distributed_apps)
  • 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
    ... a client of a remoting web service needs to be aware ... >> single instance of the beastly object and manage incoming requests ...
    (microsoft.public.dotnet.framework.aspnet.webservices)
  • Re: Pushing data from the server to the client
    ... it hits your web service or uses remoting. ... >> on the server, on your app and on the network. ... So I mocked up a facade web service on my side in .NET ... >> the remoting dll on each client machine and the stub on the server. ...
    (microsoft.public.dotnet.framework.webservices)
  • Re: Pushing data from the server to the client
    ... it hits your web service or uses remoting. ... >> on the server, on your app and on the network. ... So I mocked up a facade web service on my side in .NET ... >> the remoting dll on each client machine and the stub on the server. ...
    (microsoft.public.dotnet.framework.remoting)

Loading