You're probably coming from some of the Remoting concepts, like CAO
and SAO which differ from the Service Oriented Architecture concepts.
Look into the funcionality you need, what (the services) provides that
funcionality, the separation of responsabilitites and independence
along with autonomy of all those services. Each one of those services
with their operations provide funcionalities that implement the
requirements you have on your project.
You need to re-think the architecture of your solution.
Tiago Halm
On Apr 3, 8:35*pm, JIGNESH <JIGN...@xxxxxx> wrote:
| Quote: |  | |
|
> We had a concept in Remoting MarshalByRef or MarshalByObject
> It sounds to me *like MarshalByObject kind of need. ?
>
> Toago, am i thinking correct ?
>
>
>
> "Tiago Halm" wrote: | Quote: | | | |
> > DataContracts are just data, they are not "objects", so there is no behavior
> > involved. Only the service exibits functionality served by operations with
> > receive and return data.
| | | | | > | Quote: | | | |
> > What is the original funcional or technical requirement in this project?
| | | | | > | Quote: | | | |
> >Tiago Halm
| | | | | > | Quote: | | | |
> > <rajigo...@xxxxxx> wrote in message
> >news:1ae65090-b6f9-4518-855c-ac1483f19464@xxxxxx | Quote: | | | |
> > > Hi,
| | | | | | | | | | > | Quote: | | | | | Quote: | | | |
> > > I have this requirement that a web service be used to return an object
> > > that the client can call methods on. For e.g:
| | | | | | | | | | > | Quote: | | | | | Quote: | | | |
> > > WebServiceClient c = new WebServiceClient();
> > > SomeObject o = c.GetObject();
> > > o.DoSomething();
> > > o.Save();
| | | | | | | | | | > | Quote: | | | | | Quote: | | | |
> > > Is this possible with current state of WCF? *If so, how?
| | | | | | | | | | > | Quote: | | | | | Quote: | | | |
> > > Thanks!- Hide quoted text -
| | | | | | | | | | >
> - Show quoted text - | |
| | |