Remoting Client Activated Object

[JJ]

I want to create a client activated object using TcpChannel. The only way I could get it to work, though, is to provide the client with the remoted object's implementation. I'd rather not do this. I got around this by using a factory pattern, but there has to be another way. I tried using soapsuds with -nowp, but that didnt' work. Most examples deal with HttpChannels, and soapsuds, and all the examples work fine, but not with TcpChannels.

My question is: How can I create a CAO using a TcpChannel and not provide the client with the implementation of the object to be remoted without resorting to a Factory pattern

Thanks

JJ

[Allen Anderson]

check out this article I wrote on the subject for more information on
how to use a remoting assembly without providing the implementation.

http://www.glacialcomponents.com/Art...cleID=CAOGuide

Allen Anderson
http://www.glacialcomponents.com
mailto: allen@put my website url here.com

On Fri, 4 Jun 2004 16:06:02 -0700, "JJ" <my*******@mchsi.com> wrote:

I want to create a client activated object using TcpChannel. The only way I could get it to work, though, is to provide the client with the remoted object's implementation. I'd rather not do this. I got around this by using a factory pattern, but there has to be another way. I tried using soapsuds with -nowp, but that didnt' work. Most examples deal with HttpChannels, and soapsuds, and all the examples work fine, but not with TcpChannels.

My question is: How can I create a CAO using a TcpChannel and not provide the client with the implementation of the object to be remoted without resorting to a Factory pattern?

Thanks!

JJ

[JJ]

Thanks, Allen. Based on your article I guess the factory pattern I stumbled across is the recommended way to go. Thanks, again

-JJ