Re: Creating a remotable object like DCOM
- From: "Dmytro Lapshyn [MVP]" <x-code@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 25 Sep 2006 13:47:02 +0300
Jayme,
In DCOM, AFAIR it is also the server who creates the object - an interface you are given is actually only a proxy (or stub, can't remember exactly which of them runs on the client side).
--
Regards,
Dmytro Lapshyn [MVP]
http://blogs.vbcity.com/DmytroL
"Jayme Pechan" <jayme.pechan@xxxxxxxxxxxxx> wrote in message news:OwiHaFC4GHA.600@xxxxxxxxxxxxxxxxxxxxxxx
Does anyone know if it is possible to return an object from a remoting interface and have it be usable with .NET? I am trying to accomplish what I used to do in DCOM where I would call a function on an interface and it would return a new remote object. I could then call functions on that new object. When I attempt this with .NET it complains that the object has no channel sink. When I looked into the .NET configuration settings, this scenerio didn't seem to fit the 3, SingleCall, SingleInstance, or Client Initiated. The closest one I could think of was Client Initiated but it is the server that creates the object. Any ideas? Is this just not possible with .NET?
Thanks.
Jayme
.
- Follow-Ups:
- Re: Creating a remotable object like DCOM
- From: Jayme Pechan
- Re: Creating a remotable object like DCOM
- References:
- Creating a remotable object like DCOM
- From: Jayme Pechan
- Creating a remotable object like DCOM
- Prev by Date: Re: \.Net Framework
- Next by Date: Re: Issue with FileStream on network with transfers larger than 64 megabyte?
- Previous by thread: Creating a remotable object like DCOM
- Next by thread: Re: Creating a remotable object like DCOM
- Index(es):
Relevant Pages
|