Its Always nice to say what the solution is that you found ;)
-Original Message-
From: Yuval Gross [mailto:[EMAIL PROTECTED]]
Sent: 04 June 2002 04:48 PM
To: [EMAIL PROTECTED]
Subject: Re: [DOTNET] a c#/client/server/remoting design problem
i've found a solution.
thanx anyway.
i've found a solution.
thanx anyway.
Peter Laan <[EMAIL PROTECTED]> wrote: Lets see if I understand your problem. You
are conserned that the person who
writes the client might accidentaly code it wrong and create a writable
document when it shouldn't. Correct?
I was about to suggest that the
Lets see if I understand your problem. You are conserned that the person who
writes the client might accidentaly code it wrong and create a writable
document when it shouldn't. Correct?
I was about to suggest that the server created a derived class, but I just
saw that you had already tried that.
thanx for the reply
after modifying the doc, the client sends it to the server for processing
(updating it in the DB etc.)
the problem isn't that the client will try to hack my code (the client for
that matter are 3 (nice) guys sitting in a cubicle next to mine, and they
have access to the vss..
(inline)
From: "Yuval Gross" <[EMAIL PROTECTED]>
> i have the following design/implementation problem in c# / remoting:
>
> there's a document class (marshal by val), which is handed over from the
> server to the client.
>
> the client should be able to update the document, only if it's not in
>
